Transaction Details
Tx hash
b6e7f2f890c4e79d8a2c55427cffc124d4d578a1785638ef6f7c626f9bae1ffb
Tx prefix hash
d6906447e00db76fe16c45cf9d61e171825ccca93bcc4342b033bac34c81b49f
Tx public key
3d4ee7dcd43c456497c3a0e5ba3d6e2ef5f6a57006e185c2b95c252dbc3b6f92
Age [y:d:h:m:s]
05:209:09:40:44
Timestamp [UCT] (epoch)
2019-02-24 18:07:45 (1551031665)
Block
120069 (1431619 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
013d4ee7dcd43c456497c3a0e5ba3d6e2ef5f6a57006e185c2b95c252dbc3b6f92032100ee0f018bc759fb493b53d2fd3e9a0b9e7d973ecd6a3dc020fd8d1cbb5c105f06021b0000000000000000000000000090f9e17300000000000000000000
Outputs
1 output(s) for total of 19.137946431 ARQ
stealth address amount amount idx
00: 8d76d988a717f66db37285c656444716b33b65aa4d04129ed1ac984796b945cd 19.137946431 579870 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": 120087, 
  "vin": [ {
      "gen": {
        "height": 120069
      }
    }
  ], 
  "vout": [ {
      "amount": 19137946431, 
      "target": {
        "key": "8d76d988a717f66db37285c656444716b33b65aa4d04129ed1ac984796b945cd"
      }
    }
  ], 
  "extra": [ 1, 61, 78, 231, 220, 212, 60, 69, 100, 151, 195, 160, 229, 186, 61, 110, 46, 245, 246, 165, 112, 6, 225, 133, 194, 185, 92, 37, 45, 188, 59, 111, 146, 3, 33, 0, 238, 15, 1, 139, 199, 89, 251, 73, 59, 83, 210, 253, 62, 154, 11, 158, 125, 151, 62, 205, 106, 61, 192, 32, 253, 141, 28, 187, 92, 16, 95, 6, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 144, 249, 225, 115, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}