Transaction Details
Tx hash
fddb4aecdb24f14e445e01a1ed7628004e33d0d5bd0d06aa508ea3cb065c134f
Tx prefix hash
7ccdfcf2ee755e282ccaa2ba1277eb05192f40816f72e9cea2a635302b7a0b49
Tx public key
6a0db9c4fbaf9d7f681ddc7c87f3e261f749522ff79e2e62abc85c4e6b9fa2bf
Age [y:d:h:m:s]
05:320:08:21:55
Timestamp [UCT] (epoch)
2019-01-10 12:08:17 (1547122097)
Block
87757 (1510214 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
016a0db9c4fbaf9d7f681ddc7c87f3e261f749522ff79e2e62abc85c4e6b9fa2bf03210039d520af8409da7fe0e3d7d2f103b9ed2d5c33e0137c5bddd6a4f61336a4842b021b0000000000000000000000000023005aac00000000000000000000
Outputs
1 output(s) for total of 19.435238249 ARQ
stealth address amount amount idx
00: 01038b1519e48d40af205482621547e33c439e8d2d3697f1692374d7369afc27 19.435238249 433504 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": 87775, 
  "vin": [ {
      "gen": {
        "height": 87757
      }
    }
  ], 
  "vout": [ {
      "amount": 19435238249, 
      "target": {
        "key": "01038b1519e48d40af205482621547e33c439e8d2d3697f1692374d7369afc27"
      }
    }
  ], 
  "extra": [ 1, 106, 13, 185, 196, 251, 175, 157, 127, 104, 29, 220, 124, 135, 243, 226, 97, 247, 73, 82, 47, 247, 158, 46, 98, 171, 200, 92, 78, 107, 159, 162, 191, 3, 33, 0, 57, 213, 32, 175, 132, 9, 218, 127, 224, 227, 215, 210, 241, 3, 185, 237, 45, 92, 51, 224, 19, 124, 91, 221, 214, 164, 246, 19, 54, 164, 132, 43, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 35, 0, 90, 172, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}