Transaction Details
Tx hash
1b8e68c2c0ffad0cf6c3e3ffc28826f735f4b27379fbbf39621d0d346b8fcd44
Tx prefix hash
6bab30fe2b0389c60e524d22a58f18e07f98b0232de2a49fe776c93c5b9bd0dc
Tx public key
28903c935a2984b2da30c07472c51c19a4d7c7d6e4a66180f5d21a3c9c9ab0db
Age [y:d:h:m:s]
05:251:17:38:35
Timestamp [UCT] (epoch)
2019-03-19 19:09:52 (1553022592)
Block
136523 (1461215 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
0128903c935a2984b2da30c07472c51c19a4d7c7d6e4a66180f5d21a3c9c9ab0db032100a05a6ad847a01cba2dc84d4c99eb161d859ad5132b86cdcb3a0cb050f228820a021b00000000000000000000000000919dbf5c00000000000000000000
Outputs
1 output(s) for total of 18.988494158 ARQ
stealth address amount amount idx
00: edcd14778aa90cc50da2e56e3735c5e8086480a9b5758714f1b1ef0414d98c9e 18.988494158 638136 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": 136541, 
  "vin": [ {
      "gen": {
        "height": 136523
      }
    }
  ], 
  "vout": [ {
      "amount": 18988494158, 
      "target": {
        "key": "edcd14778aa90cc50da2e56e3735c5e8086480a9b5758714f1b1ef0414d98c9e"
      }
    }
  ], 
  "extra": [ 1, 40, 144, 60, 147, 90, 41, 132, 178, 218, 48, 192, 116, 114, 197, 28, 25, 164, 215, 199, 214, 228, 166, 97, 128, 245, 210, 26, 60, 156, 154, 176, 219, 3, 33, 0, 160, 90, 106, 216, 71, 160, 28, 186, 45, 200, 77, 76, 153, 235, 22, 29, 133, 154, 213, 19, 43, 134, 205, 203, 58, 12, 176, 80, 242, 40, 130, 10, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 145, 157, 191, 92, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}