Transaction Details
Tx hash
5251de37eef6dfd5fbd9428139b1c85a5a145a1525181a17643577dddd7f4f4d
Tx prefix hash
821ea00461912c4a6eaff67521b2d1c17fc6f1637c32bfb7c6de4e1bec09c525
Tx public key
807175a7b4906d535f73b44dda4fe72772752ae635840a4b8f4f2dc2e9a958b3
Age [y:d:h:m:s]
05:246:13:21:27
Timestamp [UCT] (epoch)
2019-03-26 19:09:00 (1553627340)
Block
141501 (1457544 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
01807175a7b4906d535f73b44dda4fe72772752ae635840a4b8f4f2dc2e9a958b3032100ff713be54da3b8a47e17cce9e8c10a1314b2e774f138073ec4b6f3d3f8f81da0021b0000000000000000000000000009317d8c00000000000000000000
Outputs
1 output(s) for total of 18.943360969 ARQ
stealth address amount amount idx
00: 22b2e3a563700ad39f6532013b8e862ffc8a81560c3b576a839b66b6c6a4907e 18.943360969 652462 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": 141519, 
  "vin": [ {
      "gen": {
        "height": 141501
      }
    }
  ], 
  "vout": [ {
      "amount": 18943360969, 
      "target": {
        "key": "22b2e3a563700ad39f6532013b8e862ffc8a81560c3b576a839b66b6c6a4907e"
      }
    }
  ], 
  "extra": [ 1, 128, 113, 117, 167, 180, 144, 109, 83, 95, 115, 180, 77, 218, 79, 231, 39, 114, 117, 42, 230, 53, 132, 10, 75, 143, 79, 45, 194, 233, 169, 88, 179, 3, 33, 0, 255, 113, 59, 229, 77, 163, 184, 164, 126, 23, 204, 233, 232, 193, 10, 19, 20, 178, 231, 116, 241, 56, 7, 62, 196, 182, 243, 211, 248, 248, 29, 160, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 9, 49, 125, 140, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}