Transaction Details
Tx hash
3f8a4f7be1b26095dbd137da209eb12851bd919e1a4cf9d133e4fa79f018e1b1
Tx prefix hash
44c0173bf2a1c11e65ec451d525d8951a09fef37492ebcf6601335c999482fdf
Tx public key
6a2ead7925c401f9c9ec01271161cbe874c20829224861c35ba028378fcca8ee
Age [y:d:h:m:s]
05:320:21:52:18
Timestamp [UCT] (epoch)
2019-01-13 18:50:09 (1547405409)
Block
90116 (1510586 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
016a2ead7925c401f9c9ec01271161cbe874c20829224861c35ba028378fcca8ee032100ecbb50a0947a536c3cfe82750b68b9869884e9a0838c5aef21eff55b7138cd55021b000000000000000000000000001579412400000000000000000000
Outputs
1 output(s) for total of 19.413443002 ARQ
stealth address amount amount idx
00: 0bf66a21564788f767a818a98e181ca10961b3aa0c55cdaee7b80a28950dd5a1 19.413443002 445212 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": 90134, 
  "vin": [ {
      "gen": {
        "height": 90116
      }
    }
  ], 
  "vout": [ {
      "amount": 19413443002, 
      "target": {
        "key": "0bf66a21564788f767a818a98e181ca10961b3aa0c55cdaee7b80a28950dd5a1"
      }
    }
  ], 
  "extra": [ 1, 106, 46, 173, 121, 37, 196, 1, 249, 201, 236, 1, 39, 17, 97, 203, 232, 116, 194, 8, 41, 34, 72, 97, 195, 91, 160, 40, 55, 143, 204, 168, 238, 3, 33, 0, 236, 187, 80, 160, 148, 122, 83, 108, 60, 254, 130, 117, 11, 104, 185, 134, 152, 132, 233, 160, 131, 140, 90, 239, 33, 239, 245, 91, 113, 56, 205, 85, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 21, 121, 65, 36, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}