Transaction Details
Tx hash
32dba3a9bd762ec8c856a17de663b0732a9d808e7476f19f47d64dfb3b540e64
Tx prefix hash
387bcb4153269205f9fea00f590c592bf0199e3e5e5a974ec9c1c1e60c5c9bba
Tx public key
0e8e6f04c17f41e7e89060a71763e5fa42dc5ae1f1c11bb0afa2c5cf37baf10d
Age [y:d:h:m:s]
05:269:16:38:01
Timestamp [UCT] (epoch)
2019-01-11 11:45:50 (1547207150)
Block
88458 (1474468 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
010e8e6f04c17f41e7e89060a71763e5fa42dc5ae1f1c11bb0afa2c5cf37baf10d032100f064bb6ebbd8561a938bbb9a6319f9f4add36491db1e3f32fdae9ef661e5762b021b000000000000000000000000002aed5dbe00000000000000000000
Outputs
1 output(s) for total of 19.428602862 ARQ
stealth address amount amount idx
00: 32da46a68e5af3f564e8408244b5cc6b46d972591772ae76e601a85f1f6999cc 19.428602862 437088 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": 88476, 
  "vin": [ {
      "gen": {
        "height": 88458
      }
    }
  ], 
  "vout": [ {
      "amount": 19428602862, 
      "target": {
        "key": "32da46a68e5af3f564e8408244b5cc6b46d972591772ae76e601a85f1f6999cc"
      }
    }
  ], 
  "extra": [ 1, 14, 142, 111, 4, 193, 127, 65, 231, 232, 144, 96, 167, 23, 99, 229, 250, 66, 220, 90, 225, 241, 193, 27, 176, 175, 162, 197, 207, 55, 186, 241, 13, 3, 33, 0, 240, 100, 187, 110, 187, 216, 86, 26, 147, 139, 187, 154, 99, 25, 249, 244, 173, 211, 100, 145, 219, 30, 63, 50, 253, 174, 158, 246, 97, 229, 118, 43, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 42, 237, 93, 190, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}