Transaction Details
Tx hash
f67c71bdf9f103614e8d2b62b623b44e02471aaa52af5da8bd259a6d62c31e3d
Tx prefix hash
087895a83480cc6fe4ea09042a09a5ee15c18150d17e637ba51c9a4c24ba494e
Tx public key
004f9c4f62350fd93e1b411a707e21aa6e40f50c4a3dbee4cf10e57584b813c7
Age [y:d:h:m:s]
05:112:21:58:41
Timestamp [UCT] (epoch)
2019-08-11 14:49:47 (1565534987)
Block
240058 (1361914 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
01004f9c4f62350fd93e1b411a707e21aa6e40f50c4a3dbee4cf10e57584b813c70321003eef658f9132baf81da46b54b8c548e04bf44743a5b172e5132e6c89c0ee73d4021b00000000000000000000000000a5fd0e1700000000000000000000
Outputs
1 output(s) for total of 18.074033151 ARQ
stealth address amount amount idx
00: e47c3c7ed5825aaee19dab4776f85c311c1a52f1d2ef9f957b2f0c7d705ea533 18.074033151 1096311 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": 240076, 
  "vin": [ {
      "gen": {
        "height": 240058
      }
    }
  ], 
  "vout": [ {
      "amount": 18074033151, 
      "target": {
        "key": "e47c3c7ed5825aaee19dab4776f85c311c1a52f1d2ef9f957b2f0c7d705ea533"
      }
    }
  ], 
  "extra": [ 1, 0, 79, 156, 79, 98, 53, 15, 217, 62, 27, 65, 26, 112, 126, 33, 170, 110, 64, 245, 12, 74, 61, 190, 228, 207, 16, 229, 117, 132, 184, 19, 199, 3, 33, 0, 62, 239, 101, 143, 145, 50, 186, 248, 29, 164, 107, 84, 184, 197, 72, 224, 75, 244, 71, 67, 165, 177, 114, 229, 19, 46, 108, 137, 192, 238, 115, 212, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 165, 253, 14, 23, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}