Transaction Details
Tx hash
0d49ad49b46181ed9b8ec54c51bf47ed3d671468bef1c8f3685feae4a1c17323
Tx prefix hash
3378c7d977ff88863f4085e59fdb6d9be5fb306e91b5f08fdc96dfd8b927f88d
Tx public key
ab376224274270935c0ce952fca2da5267b99873f08daf88c4d7f1aff60849cf
Age [y:d:h:m:s]
05:258:20:35:46
Timestamp [UCT] (epoch)
2019-01-22 17:43:03 (1548178983)
Block
96506 (1466716 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
01ab376224274270935c0ce952fca2da5267b99873f08daf88c4d7f1aff60849cf0321008d38ecdd752666f6c61cb06ca03e24821a7049d7ea1cca3ddd759cc5b692ddf3021b000000000000000000000000001b82635b00000000000000000000
Outputs
1 output(s) for total of 19.354186801 ARQ
stealth address amount amount idx
00: a90381155b5048ae9bb89ae68a5d9eef1dede22703e05749e5d8ef47aa222e96 19.354186801 476220 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": 96524, 
  "vin": [ {
      "gen": {
        "height": 96506
      }
    }
  ], 
  "vout": [ {
      "amount": 19354186801, 
      "target": {
        "key": "a90381155b5048ae9bb89ae68a5d9eef1dede22703e05749e5d8ef47aa222e96"
      }
    }
  ], 
  "extra": [ 1, 171, 55, 98, 36, 39, 66, 112, 147, 92, 12, 233, 82, 252, 162, 218, 82, 103, 185, 152, 115, 240, 141, 175, 136, 196, 215, 241, 175, 246, 8, 73, 207, 3, 33, 0, 141, 56, 236, 221, 117, 38, 102, 246, 198, 28, 176, 108, 160, 62, 36, 130, 26, 112, 73, 215, 234, 28, 202, 61, 221, 117, 156, 197, 182, 146, 221, 243, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 27, 130, 99, 91, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}