Transaction Details
Tx hash
af8bf9e3d27625ed362f986c27af30ad14de2b8cbda6b7f4e3023d14d23fd0d5
Tx prefix hash
ac3dfed10cf1100a2f0fcd7e4e7047dc9c6d47ff53a3e0f042755d9c1a47a472
Tx public key
a12c0d0871aafa2c6b0d90fec8f04b9d15c8483e76908be2bbeddb3d91c36f58
Age [y:d:h:m:s]
05:266:20:30:25
Timestamp [UCT] (epoch)
2019-01-14 06:54:03 (1547448843)
Block
90467 (1472433 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
01a12c0d0871aafa2c6b0d90fec8f04b9d15c8483e76908be2bbeddb3d91c36f580321005d100a3313d01c90b4b2342fafd5d0f967ea40bcdce54d216307cbe62abfa06f021b0000000000000000000000000027c1c00500000000000000000000
Outputs
1 output(s) for total of 19.410108611 ARQ
stealth address amount amount idx
00: a751d07d877b9c2b7f76943a1326f3239939a5a9e4ddf274e896627212f01182 19.410108611 446691 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": 90485, 
  "vin": [ {
      "gen": {
        "height": 90467
      }
    }
  ], 
  "vout": [ {
      "amount": 19410108611, 
      "target": {
        "key": "a751d07d877b9c2b7f76943a1326f3239939a5a9e4ddf274e896627212f01182"
      }
    }
  ], 
  "extra": [ 1, 161, 44, 13, 8, 113, 170, 250, 44, 107, 13, 144, 254, 200, 240, 75, 157, 21, 200, 72, 62, 118, 144, 139, 226, 187, 237, 219, 61, 145, 195, 111, 88, 3, 33, 0, 93, 16, 10, 51, 19, 208, 28, 144, 180, 178, 52, 47, 175, 213, 208, 249, 103, 234, 64, 188, 220, 229, 77, 33, 99, 7, 203, 230, 42, 191, 160, 111, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 39, 193, 192, 5, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}