For RingCT transactions, outputs' amounts are also decoded
Tx private key can be obtained using get_tx_key
command in hashmonkey-wallet-cli command line tool
Tx hash: ea6e2476493164274711af16376f543457b8e2d55d208e7a046b3bd82fe596c3
Tx prefix hash: d5eff90ed12f570de09ef875789fdf26b5ca444e3ac4a0dcf66a23a89e033af2
Tx public key: a4b5072c6006c8a13b7d2cd92564edede775ac6b8ff050bd3b5e9314bebd2746
| Timestamp: 1780075369 | Timestamp [UTC]: 2026-05-29 17:22:49 | Age [y:d:h:m:s]: 00:010:05:56:04 |
| Block: 4695 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3191 | RingCT/type: yes/0 |
| Extra: 01a4b5072c6006c8a13b7d2cd92564edede775ac6b8ff050bd3b5e9314bebd274602090000000126697be300 | ||
1 output(s) for total of 34.870768737286 HMNY
| stealth address | amount | amount idx | tag |
| 00: f806ec3e632c65d0dba3a31ea0fe18316d3d902a4f62c8ef9be84aa141f35cd6 | 34.870768737286 | 5899 of 0 | <08> |
Check which outputs belong to given HMNY address/subaddress and viewkey
For RingCT transactions, outputs' amounts are also decoded
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 HMNY in this transaction
Tx private key can be obtained using get_tx_key
command in hashmonkey-wallet-cli command line tool
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": 4755,
"vin": [ {
"gen": {
"height": 4695
}
}
],
"vout": [ {
"amount": 34870768737286,
"target": {
"tagged_key": {
"key": "f806ec3e632c65d0dba3a31ea0fe18316d3d902a4f62c8ef9be84aa141f35cd6",
"view_tag": "08"
}
}
}
],
"extra": [ 1, 164, 181, 7, 44, 96, 6, 200, 161, 59, 125, 44, 217, 37, 100, 237, 237, 231, 117, 172, 107, 143, 240, 80, 189, 59, 94, 147, 20, 190, 189, 39, 70, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}