Transaction Details
Tx hash
d5cfe3e0debf9fa4f18d28df410cc77779cd46d2dba85f80ab3ebd2d1d937def
Tx prefix hash
590e4a0ae7d0e6f9cbd1faca43fb07da94821d4c01522dde5ee349826ce25a19
Tx public key
1a6a05a213749b99056df4ecf2b00e8b9a5e6f6f235c7b137b7eb0b14bdfd3cf
Age [y:d:h:m:s]
05:107:09:43:35
Timestamp [UCT] (epoch)
2019-08-11 05:58:52 (1565503132)
Block
239794 (1358047 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1338 kB
Tx version
2
RingCT type
0
Extra
011a6a05a213749b99056df4ecf2b00e8b9a5e6f6f235c7b137b7eb0b14bdfd3cf0211000000e5df5814d8000000000000000000032100d4a56ccc0bee0d05e4a5b2997c90ab947ab5a982020fd4610b62342d28d65709
Outputs
1 output(s) for total of 18.075975923 ARQ
stealth address amount amount idx
00: e6f64a961208a97b75357a09e8f24cabfa9c9d63906cbefed693b4415ee25381 18.075975923 1095817 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": 239812, 
  "vin": [ {
      "gen": {
        "height": 239794
      }
    }
  ], 
  "vout": [ {
      "amount": 18075975923, 
      "target": {
        "key": "e6f64a961208a97b75357a09e8f24cabfa9c9d63906cbefed693b4415ee25381"
      }
    }
  ], 
  "extra": [ 1, 26, 106, 5, 162, 19, 116, 155, 153, 5, 109, 244, 236, 242, 176, 14, 139, 154, 94, 111, 111, 35, 92, 123, 19, 123, 126, 176, 177, 75, 223, 211, 207, 2, 17, 0, 0, 0, 229, 223, 88, 20, 216, 0, 0, 0, 0, 0, 0, 0, 0, 0, 3, 33, 0, 212, 165, 108, 204, 11, 238, 13, 5, 228, 165, 178, 153, 124, 144, 171, 148, 122, 181, 169, 130, 2, 15, 212, 97, 11, 98, 52, 45, 40, 214, 87, 9
  ], 
  "rct_signatures": {
    "type": 0
  }
}