Transaction Details
Tx hash
a9f76d45b3c869c8b687510a9845f316eb8b65aa6a1acb3490ebaf5b2cfb72fe
Tx prefix hash
d62a0d0ac47b57b5953b1f33bb0d82502d13e54ebb35eab34711a1578a13ccb2
Tx public key
8b237c952624da328c86ef1e80cf0b9a9e3c2b52b57dc102223d844c6fb2d4ab
Age [y:d:h:m:s]
05:233:03:36:52
Timestamp [UCT] (epoch)
2019-04-09 03:50:41 (1554781841)
Block
150953 (1448059 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
018b237c952624da328c86ef1e80cf0b9a9e3c2b52b57dc102223d844c6fb2d4ab032100ddc1c1b08e512a92e59e1c23ecfb519d7c7440c9371fbd869f84964ca869c16f021b000000000000000000000000007c9c3e8400000000000000000000
Outputs
1 output(s) for total of 18.858174109 ARQ
stealth address amount amount idx
00: e4efbf2aa4486aafd9bdfc574294bbd263abc9f34b9ec4664cf14bcf6f838916 18.858174109 691133 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": 150971, 
  "vin": [ {
      "gen": {
        "height": 150953
      }
    }
  ], 
  "vout": [ {
      "amount": 18858174109, 
      "target": {
        "key": "e4efbf2aa4486aafd9bdfc574294bbd263abc9f34b9ec4664cf14bcf6f838916"
      }
    }
  ], 
  "extra": [ 1, 139, 35, 124, 149, 38, 36, 218, 50, 140, 134, 239, 30, 128, 207, 11, 154, 158, 60, 43, 82, 181, 125, 193, 2, 34, 61, 132, 76, 111, 178, 212, 171, 3, 33, 0, 221, 193, 193, 176, 142, 81, 42, 146, 229, 158, 28, 35, 236, 251, 81, 157, 124, 116, 64, 201, 55, 31, 189, 134, 159, 132, 150, 76, 168, 105, 193, 111, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 124, 156, 62, 132, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}