Transaction Details
Tx hash
29f025f472edf0983f88ff2fd04008e3ed0789e977da957dde43e2a6daacfc00
Tx prefix hash
05921c5989d96825613610c2a27e62b8bbcf2c32207a56e99d8900b9b1226773
Tx public key
4722fce0026ff1209084e1742cacd29d3b815a8d7e8a8678056f1656bffc0043
Age [y:d:h:m:s]
05:322:23:04:14
Timestamp [UCT] (epoch)
2019-01-12 00:23:13 (1547252593)
Block
88823 (1512066 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
014722fce0026ff1209084e1742cacd29d3b815a8d7e8a8678056f1656bffc00430321006925afb657939ee982b560ae49717bd71ddeaf37e9bc3ec1fb03606b4708b360021b000000000000000000000000000b866e0a00000000000000000000
Outputs
1 output(s) for total of 19.425314933 ARQ
stealth address amount amount idx
00: 4ba3bf2bda4458696f0093d52e26c862ac492a1e9e562e90b025d7dbd54793ce 19.425314933 439230 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": 88841, 
  "vin": [ {
      "gen": {
        "height": 88823
      }
    }
  ], 
  "vout": [ {
      "amount": 19425314933, 
      "target": {
        "key": "4ba3bf2bda4458696f0093d52e26c862ac492a1e9e562e90b025d7dbd54793ce"
      }
    }
  ], 
  "extra": [ 1, 71, 34, 252, 224, 2, 111, 241, 32, 144, 132, 225, 116, 44, 172, 210, 157, 59, 129, 90, 141, 126, 138, 134, 120, 5, 111, 22, 86, 191, 252, 0, 67, 3, 33, 0, 105, 37, 175, 182, 87, 147, 158, 233, 130, 181, 96, 174, 73, 113, 123, 215, 29, 222, 175, 55, 233, 188, 62, 193, 251, 3, 96, 107, 71, 8, 179, 96, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 11, 134, 110, 10, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}