Transaction Details
Tx hash
1459efc4a6cc346c0a37151b96ed2aea5e714af4d8092f6dcb76eb3564beaf8d
Tx prefix hash
f687c9f5ac63f362b9ac027c80a73895a074215a2e618a934a3ae36972f920b2
Tx public key
6d7264bdce8ca0cf1c1d268da9c179c71d6d7a950e42d24fbee37c72e77b08ea
Age [y:d:h:m:s]
05:230:00:50:08
Timestamp [UCT] (epoch)
2019-02-19 06:41:21 (1550558481)
Block
116150 (1446156 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
016d7264bdce8ca0cf1c1d268da9c179c71d6d7a950e42d24fbee37c72e77b08ea03210057ef30667ee2444b724875dcf4a4de04d4d41ba0b0de46c2b515b2319e386ac4021b000000000000000000000000002efa8e3f00000000000000000000
Outputs
1 output(s) for total of 19.173743265 ARQ
stealth address amount amount idx
00: 816144828f06080bfb77579c40af8308825c32b3a6a5e4c64947dfee9b7f6bfb 19.173743265 565032 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": 116168, 
  "vin": [ {
      "gen": {
        "height": 116150
      }
    }
  ], 
  "vout": [ {
      "amount": 19173743265, 
      "target": {
        "key": "816144828f06080bfb77579c40af8308825c32b3a6a5e4c64947dfee9b7f6bfb"
      }
    }
  ], 
  "extra": [ 1, 109, 114, 100, 189, 206, 140, 160, 207, 28, 29, 38, 141, 169, 193, 121, 199, 29, 109, 122, 149, 14, 66, 210, 79, 190, 227, 124, 114, 231, 123, 8, 234, 3, 33, 0, 87, 239, 48, 102, 126, 226, 68, 75, 114, 72, 117, 220, 244, 164, 222, 4, 212, 212, 27, 160, 176, 222, 70, 194, 181, 21, 178, 49, 158, 56, 106, 196, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 46, 250, 142, 63, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}