Transaction Details
Tx hash
fd1dfaa91c973b03d4d59f0a0d756903ef9909f021974b5d9cdea2f0b7c813f6
Tx prefix hash
72e9003a7e6bf1af11a9f01cb61f18306ca5d00def79f1ac9cd6ac31ec5f8b35
Tx public key
e494e90d0d6c8c9f7de8848b4bcbc1073ae15d6e4e7a70939e6da82668e084f7
Age [y:d:h:m:s]
05:159:19:50:00
Timestamp [UCT] (epoch)
2019-06-24 01:40:27 (1561340427)
Block
205178 (1395653 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
01e494e90d0d6c8c9f7de8848b4bcbc1073ae15d6e4e7a70939e6da82668e084f703210034469dce57a052b87e2f84a4111eaa10b6fafbc09261e16fd5fb3ab1164248d0021b00000000000000000000000000778b465d00000000000000000000
Outputs
1 output(s) for total of 18.376935225 ARQ
stealth address amount amount idx
00: f8a38e0748c7ef86a5d55ea83d16aa4d0e4094ffdb9a195aa6292e3b3ae789a9 18.376935225 937949 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": 205196, 
  "vin": [ {
      "gen": {
        "height": 205178
      }
    }
  ], 
  "vout": [ {
      "amount": 18376935225, 
      "target": {
        "key": "f8a38e0748c7ef86a5d55ea83d16aa4d0e4094ffdb9a195aa6292e3b3ae789a9"
      }
    }
  ], 
  "extra": [ 1, 228, 148, 233, 13, 13, 108, 140, 159, 125, 232, 132, 139, 75, 203, 193, 7, 58, 225, 93, 110, 78, 122, 112, 147, 158, 109, 168, 38, 104, 224, 132, 247, 3, 33, 0, 52, 70, 157, 206, 87, 160, 82, 184, 126, 47, 132, 164, 17, 30, 170, 16, 182, 250, 251, 192, 146, 97, 225, 111, 213, 251, 58, 177, 22, 66, 72, 208, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 119, 139, 70, 93, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}