Transaction Details
Tx hash
af007318055fb06fe4f6e3cc58f395adbb517dbcd47262a4cb6c3e1a0b9b2789
Tx prefix hash
bc7d4376a8f623ee586188ab6854012246fec731e64ee8b635b9445680346d31
Tx public key
c5e64f27deb365db9c6b6710dc1dd9387c5ba2c7b54927ffc81ca8660c6a2487
Age [y:d:h:m:s]
05:320:23:08:16
Timestamp [UCT] (epoch)
2019-01-13 13:37:12 (1547386632)
Block
89936 (1510647 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
01c5e64f27deb365db9c6b6710dc1dd9387c5ba2c7b54927ffc81ca8660c6a2487032100d798d3db06e74a0128531a641c1fea7ce21e6f968a545d34550192b3badef7eb021b000000000000000000000000001d79412400000000000000000000
Outputs
1 output(s) for total of 19.414915077 ARQ
stealth address amount amount idx
00: 7744f23f7ef770dee08976dc0809be2ae7357d37195fd5e73407050a2bc9e271 19.414915077 444385 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": 89954, 
  "vin": [ {
      "gen": {
        "height": 89936
      }
    }
  ], 
  "vout": [ {
      "amount": 19414915077, 
      "target": {
        "key": "7744f23f7ef770dee08976dc0809be2ae7357d37195fd5e73407050a2bc9e271"
      }
    }
  ], 
  "extra": [ 1, 197, 230, 79, 39, 222, 179, 101, 219, 156, 107, 103, 16, 220, 29, 217, 56, 124, 91, 162, 199, 181, 73, 39, 255, 200, 28, 168, 102, 12, 106, 36, 135, 3, 33, 0, 215, 152, 211, 219, 6, 231, 74, 1, 40, 83, 26, 100, 28, 31, 234, 124, 226, 30, 111, 150, 138, 84, 93, 52, 85, 1, 146, 179, 186, 222, 247, 235, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 29, 121, 65, 36, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}