Transaction Details
Tx hash
00a4ff20d553b9519ebbdc4dbfd3fa2ae5344078ee000461e36237a7240be3b3
Tx prefix hash
c0d3483c746f78cd41ab32495bc23a06f683b1a126ed8d72635384d4a9fb27a0
Tx public key
794ef2cd95b6a485b1514be9edf0071cfdac2b38cfe730e9e59abebd4d415729
Age [y:d:h:m:s]
05:242:13:04:12
Timestamp [UCT] (epoch)
2019-03-30 04:32:15 (1553920335)
Block
143895 (1454707 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
01794ef2cd95b6a485b1514be9edf0071cfdac2b38cfe730e9e59abebd4d415729032100690c22b0ddde244d8ae2ebe3e4dd273c224289e851badaeead617ae6e3558d57021b0000000000000000000000000006e71c8000000000000000000000
Outputs
1 output(s) for total of 18.921968074 ARQ
stealth address amount amount idx
00: 3ce3d0a73236efd0d3a28c81c8aa402bac8449031c468bfa59100e02ee4f32b3 18.921968074 661250 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": 143913, 
  "vin": [ {
      "gen": {
        "height": 143895
      }
    }
  ], 
  "vout": [ {
      "amount": 18921968074, 
      "target": {
        "key": "3ce3d0a73236efd0d3a28c81c8aa402bac8449031c468bfa59100e02ee4f32b3"
      }
    }
  ], 
  "extra": [ 1, 121, 78, 242, 205, 149, 182, 164, 133, 177, 81, 75, 233, 237, 240, 7, 28, 253, 172, 43, 56, 207, 231, 48, 233, 229, 154, 190, 189, 77, 65, 87, 41, 3, 33, 0, 105, 12, 34, 176, 221, 222, 36, 77, 138, 226, 235, 227, 228, 221, 39, 60, 34, 66, 137, 232, 81, 186, 218, 238, 173, 97, 122, 230, 227, 85, 141, 87, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 6, 231, 28, 128, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}