Transaction Details
Tx hash
bdf2139e3cb2c755ddbe5c22bad30ffe1541b39b59d8c2ff8c8f2fe100e1b03d
Tx prefix hash
d68fd26222f361f160fb204a8a49b5a6d4c61ef5076a8f43a68a5949c066f0e8
Tx public key
dc390111fd60983a9df9197f68a7398a5a5472af0a3d1f8a22a41b092098e0f7
Age [y:d:h:m:s]
05:149:16:54:43
Timestamp [UCT] (epoch)
2019-05-10 23:41:29 (1557531689)
Block
173712 (1388852 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
01dc390111fd60983a9df9197f68a7398a5a5472af0a3d1f8a22a41b092098e0f703210044b482e625f5cb0825ca017f596b0a010e008e557ed044a6c26f522ae751864d021b000000000000000000000000009601d3b100000000000000000000
Outputs
1 output(s) for total of 18.654625290 ARQ
stealth address amount amount idx
00: a4f85ae61e5ac77bfd6df24221190c397e3dabf4314349fdf24273bcbe55d3f6 18.654625290 786856 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": 173730, 
  "vin": [ {
      "gen": {
        "height": 173712
      }
    }
  ], 
  "vout": [ {
      "amount": 18654625290, 
      "target": {
        "key": "a4f85ae61e5ac77bfd6df24221190c397e3dabf4314349fdf24273bcbe55d3f6"
      }
    }
  ], 
  "extra": [ 1, 220, 57, 1, 17, 253, 96, 152, 58, 157, 249, 25, 127, 104, 167, 57, 138, 90, 84, 114, 175, 10, 61, 31, 138, 34, 164, 27, 9, 32, 152, 224, 247, 3, 33, 0, 68, 180, 130, 230, 37, 245, 203, 8, 37, 202, 1, 127, 89, 107, 10, 1, 14, 0, 142, 85, 126, 208, 68, 166, 194, 111, 82, 42, 231, 81, 134, 77, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 150, 1, 211, 177, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}