Transaction Details
Tx hash
f837cff30431718d787588bf86b2bc59f0c74a9a29eba32b70648861119243d1
Tx prefix hash
a218dee395f0bf4752107c02c57419345006fd41e3c687a626f3a947da368473
Tx public key
26418a22e39e4fabdb1452d62ad54d656525e6dbe60512f94fd963f5c1d4e715
Age [y:d:h:m:s]
05:358:01:04:26
Timestamp [UCT] (epoch)
2018-12-07 09:50:01 (1544176201)
Block
63516 (1537011 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1328 kB
Tx version
2
RingCT type
0
Extra
0126418a22e39e4fabdb1452d62ad54d656525e6dbe60512f94fd963f5c1d4e715032100f352d7da13e9d6eee47cc59504bc5c2e38ce49654cbce42afaad9deea0ba9fba021000000020fc1c01000000000000000000
Outputs
1 output(s) for total of 19.661052134 ARQ
stealth address amount amount idx
00: cf83f79e1e2b24aaacedd98d8f3619da26d5c474c006a686ba204865c299fda7 19.661052134 341242 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": 63534, 
  "vin": [ {
      "gen": {
        "height": 63516
      }
    }
  ], 
  "vout": [ {
      "amount": 19661052134, 
      "target": {
        "key": "cf83f79e1e2b24aaacedd98d8f3619da26d5c474c006a686ba204865c299fda7"
      }
    }
  ], 
  "extra": [ 1, 38, 65, 138, 34, 227, 158, 79, 171, 219, 20, 82, 214, 42, 213, 77, 101, 101, 37, 230, 219, 230, 5, 18, 249, 79, 217, 99, 245, 193, 212, 231, 21, 3, 33, 0, 243, 82, 215, 218, 19, 233, 214, 238, 228, 124, 197, 149, 4, 188, 92, 46, 56, 206, 73, 101, 76, 188, 228, 42, 250, 173, 157, 238, 160, 186, 159, 186, 2, 16, 0, 0, 0, 32, 252, 28, 1, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}