Transaction Details
Tx hash
c644c896d48325e23a0657bd17b8fbc581a5dcc3a11ac4a9ba901bf18e0aef0c
Tx prefix hash
f53384fa0d7ed8665c56aac757bf023db301e974fa543ddd4e10aa6b201466cb
Tx public key
ab8beff1737d02fee811056225efc61bce491de85f2df8eb5d909d364fe52d13
Age [y:d:h:m:s]
05:318:16:46:45
Timestamp [UCT] (epoch)
2019-01-11 18:25:41 (1547231141)
Block
88645 (1509050 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
01ab8beff1737d02fee811056225efc61bce491de85f2df8eb5d909d364fe52d130321002711ee703b2ffeaf895b19a04ef394c5db9f5b430a3db40fa5067c070ca9d216021b000000000000000000000000001e866e0a00000000000000000000
Outputs
1 output(s) for total of 19.426870518 ARQ
stealth address amount amount idx
00: 1a577af44b2e4fb3ef6453a89de38212e9ee0cd5acac8b01c990b2555db61619 19.426870518 438220 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": 88663, 
  "vin": [ {
      "gen": {
        "height": 88645
      }
    }
  ], 
  "vout": [ {
      "amount": 19426870518, 
      "target": {
        "key": "1a577af44b2e4fb3ef6453a89de38212e9ee0cd5acac8b01c990b2555db61619"
      }
    }
  ], 
  "extra": [ 1, 171, 139, 239, 241, 115, 125, 2, 254, 232, 17, 5, 98, 37, 239, 198, 27, 206, 73, 29, 232, 95, 45, 248, 235, 93, 144, 157, 54, 79, 229, 45, 19, 3, 33, 0, 39, 17, 238, 112, 59, 47, 254, 175, 137, 91, 25, 160, 78, 243, 148, 197, 219, 159, 91, 67, 10, 61, 180, 15, 165, 6, 124, 7, 12, 169, 210, 22, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 30, 134, 110, 10, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}