Transaction Details
Tx hash
573fec5a90ec7efa4e6576e08dc846b9ea410e0d934e88d62f4b2a2eb0a4c4cd
Tx prefix hash
ddd92df0b3027cff6e381890dd51c26b9c333f7d1909bc278f009072c5434a84
Tx public key
a6ec3b92721a615512ea34f8b89d9dc2acb9526a0e8f51fe53f9711ddb3fa1ca
Age [y:d:h:m:s]
05:211:22:16:25
Timestamp [UCT] (epoch)
2019-03-10 11:09:30 (1552216170)
Block
129871 (1433212 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
01a6ec3b92721a615512ea34f8b89d9dc2acb9526a0e8f51fe53f9711ddb3fa1ca03210089d5d2c0f09b6e0714e6ea3731ddbbf6a5090885055ebc4e16813c136f11624d021b000000000000000000000000001b7eb18e00000000000000000000
Outputs
1 output(s) for total of 19.048705433 ARQ
stealth address amount amount idx
00: df392da3fff963df173a9b93ab41039bc49a28b2a4600b57b005448abb510c2f 19.048705433 617462 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": 129889, 
  "vin": [ {
      "gen": {
        "height": 129871
      }
    }
  ], 
  "vout": [ {
      "amount": 19048705433, 
      "target": {
        "key": "df392da3fff963df173a9b93ab41039bc49a28b2a4600b57b005448abb510c2f"
      }
    }
  ], 
  "extra": [ 1, 166, 236, 59, 146, 114, 26, 97, 85, 18, 234, 52, 248, 184, 157, 157, 194, 172, 185, 82, 106, 14, 143, 81, 254, 83, 249, 113, 29, 219, 63, 161, 202, 3, 33, 0, 137, 213, 210, 192, 240, 155, 110, 7, 20, 230, 234, 55, 49, 221, 187, 246, 165, 9, 8, 133, 5, 94, 188, 78, 22, 129, 60, 19, 111, 17, 98, 77, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 27, 126, 177, 142, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}