Transaction Details
Tx hash
00b213c68618f9a079f1f9f7f0eb3565cf84c9ce4c8ff5ee1852e826b7a7ddac
Tx prefix hash
dc93a7060f0c07f2ad1239cfd729f3643641fe47009456090ee7f88daa6cfd7c
Tx public key
9a5ff8e40ee9db929d2f0fde34c5eeb6f33fdf58e789c9f24bccd4d8475efb1c
Age [y:d:h:m:s]
05:317:21:35:19
Timestamp [UCT] (epoch)
2019-01-13 19:50:00 (1547409000)
Block
90146 (1508450 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1367 kB
Tx version
2
RingCT type
0
Extra
019a5ff8e40ee9db929d2f0fde34c5eeb6f33fdf58e789c9f24bccd4d8475efb1c032107a8d6e586f6e87c84a7cf58a97e0c69a808d659db7f0902abfd03a7bdc281194c02140000000104e19d00000000000000000000000000
Outputs
1 output(s) for total of 19.413064285 ARQ
stealth address amount amount idx
00: 3a90e704f82f1e102d3f9f68e271b70a4dcd632214f3f72b84528a0dbe3dd6d9 19.413064285 445350 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": 90164, 
  "vin": [ {
      "gen": {
        "height": 90146
      }
    }
  ], 
  "vout": [ {
      "amount": 19413064285, 
      "target": {
        "key": "3a90e704f82f1e102d3f9f68e271b70a4dcd632214f3f72b84528a0dbe3dd6d9"
      }
    }
  ], 
  "extra": [ 1, 154, 95, 248, 228, 14, 233, 219, 146, 157, 47, 15, 222, 52, 197, 238, 182, 243, 63, 223, 88, 231, 137, 201, 242, 75, 204, 212, 216, 71, 94, 251, 28, 3, 33, 7, 168, 214, 229, 134, 246, 232, 124, 132, 167, 207, 88, 169, 126, 12, 105, 168, 8, 214, 89, 219, 127, 9, 2, 171, 253, 3, 167, 189, 194, 129, 25, 76, 2, 20, 0, 0, 0, 1, 4, 225, 157, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}