Transaction Details
Tx hash
8a8f1ff6200210d01a94348bc9b5806cc3f4356a3a630e372ebbbe4d3fdee8a3
Tx prefix hash
0832dd79812d39d44152a3cb00ee83d96b7119c960f356d0de849e24a5fbd4ac
Tx public key
861479608345629f6bdb790b54e4a0c62a23f8fda3281d999bd145f751c2111b
Age [y:d:h:m:s]
05:056:09:31:16
Timestamp [UCT] (epoch)
2019-10-04 18:53:11 (1570215191)
Block
278426 (1321915 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1338 kB
Tx version
2
RingCT type
0
Extra
01861479608345629f6bdb790b54e4a0c62a23f8fda3281d999bd145f751c2111b02110000090d9778aae10000000000000000000321006fce5f168b0f8fb513e809f8a5c0e93bf2827b4520c8f46c464a3030e8d902a2
Outputs
1 output(s) for total of 20.143113999 ARQ
stealth address amount amount idx
00: 00a8131f2fcb8c4ce08aba2023579bfe8c63a26e74f825aab26b6b7dd6d3671e 20.143113999 1252581 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": 278444, 
  "vin": [ {
      "gen": {
        "height": 278426
      }
    }
  ], 
  "vout": [ {
      "amount": 20143113999, 
      "target": {
        "key": "00a8131f2fcb8c4ce08aba2023579bfe8c63a26e74f825aab26b6b7dd6d3671e"
      }
    }
  ], 
  "extra": [ 1, 134, 20, 121, 96, 131, 69, 98, 159, 107, 219, 121, 11, 84, 228, 160, 198, 42, 35, 248, 253, 163, 40, 29, 153, 155, 209, 69, 247, 81, 194, 17, 27, 2, 17, 0, 0, 9, 13, 151, 120, 170, 225, 0, 0, 0, 0, 0, 0, 0, 0, 0, 3, 33, 0, 111, 206, 95, 22, 139, 15, 143, 181, 19, 232, 9, 248, 165, 192, 233, 59, 242, 130, 123, 69, 32, 200, 244, 108, 70, 74, 48, 48, 232, 217, 2, 162
  ], 
  "rct_signatures": {
    "type": 0
  }
}