Transaction Details
Tx hash
1ddc3bc981b448a3cf6361943e88938879472cecf2437aa313ad5f5d7907c606
Tx prefix hash
55422330d436119d3e90ed351bb9bd9057965489a147e91c732865c473a5b854
Tx public key
cc81e34e0f0b21ea8a7e381b63c2b281359e8e7117d1ec8c8880953634b9dc51
Age [y:d:h:m:s]
05:117:17:19:17
Timestamp [UCT] (epoch)
2019-08-02 05:14:10 (1564722850)
Block
233339 (1365403 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
01cc81e34e0f0b21ea8a7e381b63c2b281359e8e7117d1ec8c8880953634b9dc51032100490a09021bc57bcbd13d5bdeb187aebe3285753c5debdb2248bbef57808539de021b0000000000000000000000000236af913b00000000000000000000
Outputs
1 output(s) for total of 18.131699212 ARQ
stealth address amount amount idx
00: c5a92ec639addb5e6f9c61b59ce8fbeaad7ce38f30ed3246ef740483dc2356f4 18.131699212 1082077 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": 233357, 
  "vin": [ {
      "gen": {
        "height": 233339
      }
    }
  ], 
  "vout": [ {
      "amount": 18131699212, 
      "target": {
        "key": "c5a92ec639addb5e6f9c61b59ce8fbeaad7ce38f30ed3246ef740483dc2356f4"
      }
    }
  ], 
  "extra": [ 1, 204, 129, 227, 78, 15, 11, 33, 234, 138, 126, 56, 27, 99, 194, 178, 129, 53, 158, 142, 113, 23, 209, 236, 140, 136, 128, 149, 54, 52, 185, 220, 81, 3, 33, 0, 73, 10, 9, 2, 27, 197, 123, 203, 209, 61, 91, 222, 177, 135, 174, 190, 50, 133, 117, 60, 93, 235, 219, 34, 72, 187, 239, 87, 128, 133, 57, 222, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 2, 54, 175, 145, 59, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}