Transaction Details
Tx hash
601e9cf42bdea317c3bd58ea95367e556302a9180ee854402e6be494d93889fd
Tx prefix hash
28acdefe3d9b5e10d282c32adf05668e5b4b25cb6220eec80d9341d1d73e020e
Tx public key
d5eafd268592c22a8d0bfc2dcab6af3d323a36f199fb45c8bb802eac4e1e0536
Age [y:d:h:m:s]
05:149:11:58:48
Timestamp [UCT] (epoch)
2019-07-04 06:19:39 (1562221179)
Block
212482 (1388267 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1338 kB
Tx version
2
RingCT type
0
Extra
01d5eafd268592c22a8d0bfc2dcab6af3d323a36f199fb45c8bb802eac4e1e0536021100000031091d2b5c00000000000000000003210099bed7352ee6d33d8d2b7cb6a45c14c0fc43b401a79e4c01f17aa3dca64c2f1e
Outputs
1 output(s) for total of 18.312925814 ARQ
stealth address amount amount idx
00: 8f43ee5044093bdcab7360d5fc86f45b3fae101bc2e718fa3074df5ef6c6ce55 18.312925814 981544 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": 212500, 
  "vin": [ {
      "gen": {
        "height": 212482
      }
    }
  ], 
  "vout": [ {
      "amount": 18312925814, 
      "target": {
        "key": "8f43ee5044093bdcab7360d5fc86f45b3fae101bc2e718fa3074df5ef6c6ce55"
      }
    }
  ], 
  "extra": [ 1, 213, 234, 253, 38, 133, 146, 194, 42, 141, 11, 252, 45, 202, 182, 175, 61, 50, 58, 54, 241, 153, 251, 69, 200, 187, 128, 46, 172, 78, 30, 5, 54, 2, 17, 0, 0, 0, 49, 9, 29, 43, 92, 0, 0, 0, 0, 0, 0, 0, 0, 0, 3, 33, 0, 153, 190, 215, 53, 46, 230, 211, 61, 141, 43, 124, 182, 164, 92, 20, 192, 252, 67, 180, 1, 167, 158, 76, 1, 241, 122, 163, 220, 166, 76, 47, 30
  ], 
  "rct_signatures": {
    "type": 0
  }
}