Transaction Details
Tx hash
d82fba3aed52af8d18afa8ef746f3f005785b4e5f7335129efd20609379bb3a7
Tx prefix hash
e74a1ea5320890a0520b621096d0180a40a4ab6cccbeab144e137ab2d23709df
Tx public key
0679912b3ce5fe217c5659c45dc3e350e642f6897f19c04aa9925b736674647d
Age [y:d:h:m:s]
05:266:15:00:04
Timestamp [UCT] (epoch)
2019-01-13 12:24:25 (1547382265)
Block
89893 (1472291 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
010679912b3ce5fe217c5659c45dc3e350e642f6897f19c04aa9925b736674647d032100cccdf853bdfe5560dbc4b3f936ad8debe66f7424b44305b180053d2778db02e9021b000000000000000000000000003279412400000000000000000000
Outputs
1 output(s) for total of 19.415313164 ARQ
stealth address amount amount idx
00: 2baf36349bfcdb3a3217bacf7f6b07b7c4af80d4c7db05dfd40ecd75abd9ef68 19.415313164 444235 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": 89911, 
  "vin": [ {
      "gen": {
        "height": 89893
      }
    }
  ], 
  "vout": [ {
      "amount": 19415313164, 
      "target": {
        "key": "2baf36349bfcdb3a3217bacf7f6b07b7c4af80d4c7db05dfd40ecd75abd9ef68"
      }
    }
  ], 
  "extra": [ 1, 6, 121, 145, 43, 60, 229, 254, 33, 124, 86, 89, 196, 93, 195, 227, 80, 230, 66, 246, 137, 127, 25, 192, 74, 169, 146, 91, 115, 102, 116, 100, 125, 3, 33, 0, 204, 205, 248, 83, 189, 254, 85, 96, 219, 196, 179, 249, 54, 173, 141, 235, 230, 111, 116, 36, 180, 67, 5, 177, 128, 5, 61, 39, 120, 219, 2, 233, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 50, 121, 65, 36, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}