Transaction Details
Tx hash
bd04e9d60bf1043541e6aa279dd04adbfd890dab01b0238045a1f65834af6306
Tx prefix hash
ad7505096fed0ca017709999aa768bdc7ba2f8d2651fab0cfb7c9dfaf96df11c
Tx public key
687de0c502e9cf1387fbe813d6473090f46068dc21b2b76c201ee24cc1857a64
Age [y:d:h:m:s]
05:245:18:41:30
Timestamp [UCT] (epoch)
2019-03-29 00:15:57 (1553818557)
Block
143036 (1457012 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
01687de0c502e9cf1387fbe813d6473090f46068dc21b2b76c201ee24cc1857a64032100de6cf90728bf9d6aee023953a619b176d44f4f10402e3b2870efab27ed37098e021b0000000000000000000000000014f8923b00000000000000000000
Outputs
1 output(s) for total of 18.929500540 ARQ
stealth address amount amount idx
00: d52faf2fb3618ba5c6bf66992eaccb1a9e18afc72f9ca16d658068d9dd8dc6ce 18.929500540 658234 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": 143054, 
  "vin": [ {
      "gen": {
        "height": 143036
      }
    }
  ], 
  "vout": [ {
      "amount": 18929500540, 
      "target": {
        "key": "d52faf2fb3618ba5c6bf66992eaccb1a9e18afc72f9ca16d658068d9dd8dc6ce"
      }
    }
  ], 
  "extra": [ 1, 104, 125, 224, 197, 2, 233, 207, 19, 135, 251, 232, 19, 214, 71, 48, 144, 244, 96, 104, 220, 33, 178, 183, 108, 32, 30, 226, 76, 193, 133, 122, 100, 3, 33, 0, 222, 108, 249, 7, 40, 191, 157, 106, 238, 2, 57, 83, 166, 25, 177, 118, 212, 79, 79, 16, 64, 46, 59, 40, 112, 239, 171, 39, 237, 55, 9, 142, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 20, 248, 146, 59, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}