Transaction Details
Tx hash
dddd7b57eff4ee1484d6bcf2eea096ebed41fc9ede6458cf5ae13624e49b7d1a
Tx prefix hash
38410f51f391678d59e5bf41c0f267bc3bce54d5249029853c2a8950f6a46f61
Tx public key
4b5bf9817a0803b356336f046948bfcc73ed67bd9829fafa75bd5f6aee9633cc
Age [y:d:h:m:s]
05:329:01:51:14
Timestamp [UCT] (epoch)
2019-01-04 17:00:14 (1546621214)
Block
83639 (1516408 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
014b5bf9817a0803b356336f046948bfcc73ed67bd9829fafa75bd5f6aee9633cc0321005aaec4e69472eb83914e9cc608b6148df808a7baa67b5357383572c090e59560021b0000000000000000000000000002b8e05600000000000000000000
Outputs
1 output(s) for total of 19.473368880 ARQ
stealth address amount amount idx
00: fff9d85fb4f8dc5e185c2c16c3d2c9560903d3fcc687f79089f5d28786d82d04 19.473368880 414587 of 0

Check which outputs belong to given ARQ address/subaddress and viewkey
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side

Prove to someone that you have sent them ARQ in this transaction
Tx private key can be obtained using get_tx_key command in arqma-wallet-cli
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side

        
          {
  "version": 2, 
  "unlock_time": 83657, 
  "vin": [ {
      "gen": {
        "height": 83639
      }
    }
  ], 
  "vout": [ {
      "amount": 19473368880, 
      "target": {
        "key": "fff9d85fb4f8dc5e185c2c16c3d2c9560903d3fcc687f79089f5d28786d82d04"
      }
    }
  ], 
  "extra": [ 1, 75, 91, 249, 129, 122, 8, 3, 179, 86, 51, 111, 4, 105, 72, 191, 204, 115, 237, 103, 189, 152, 41, 250, 250, 117, 189, 95, 106, 238, 150, 51, 204, 3, 33, 0, 90, 174, 196, 230, 148, 114, 235, 131, 145, 78, 156, 198, 8, 182, 20, 141, 248, 8, 167, 186, 166, 123, 83, 87, 56, 53, 114, 192, 144, 229, 149, 96, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 2, 184, 224, 86, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}