Transaction Details
Tx hash
8b076c2b8d07791125b969de17e8394ae5d54a33b9409336b5edf70d7c474b5f
Tx prefix hash
cc0b1b615f5d7ac1b0b4d971825f06927da9037e2d50fc7b88dfe3155788dc58
Tx public key
20b656b48f3ddc14e0af27d40465e4a4a9a9b5d172f58a0620f5f299bc54d8c5
Age [y:d:h:m:s]
05:104:09:15:41
Timestamp [UCT] (epoch)
2019-08-17 04:27:48 (1566016068)
Block
244070 (1355827 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
0120b656b48f3ddc14e0af27d40465e4a4a9a9b5d172f58a0620f5f299bc54d8c50321008f83d4a9b3d0aaa3acb1ee3580b0ec5c30d03659b5fbf7dd2889b0594b84284a021b000000000000000000000000047c1522be00000000000000000000
Outputs
1 output(s) for total of 18.039157349 ARQ
stealth address amount amount idx
00: 1b91a4aae1f5d17f87df64c4495ef209a38037e21e61dbc30c13523587fdbebd 18.039157349 1103391 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": 244088, 
  "vin": [ {
      "gen": {
        "height": 244070
      }
    }
  ], 
  "vout": [ {
      "amount": 18039157349, 
      "target": {
        "key": "1b91a4aae1f5d17f87df64c4495ef209a38037e21e61dbc30c13523587fdbebd"
      }
    }
  ], 
  "extra": [ 1, 32, 182, 86, 180, 143, 61, 220, 20, 224, 175, 39, 212, 4, 101, 228, 164, 169, 169, 181, 209, 114, 245, 138, 6, 32, 245, 242, 153, 188, 84, 216, 197, 3, 33, 0, 143, 131, 212, 169, 179, 208, 170, 163, 172, 177, 238, 53, 128, 176, 236, 92, 48, 208, 54, 89, 181, 251, 247, 221, 40, 137, 176, 89, 75, 132, 40, 74, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 4, 124, 21, 34, 190, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}