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: a5911115c0477df017adab384dd524f3309fcd0a8261b36e2252d6fcfa51bc1c
Tx prefix hash: 9718d7efadf2ed1c5ef0a874288f73a5ca341def738f7aa59b031e01738d8b23
Tx public key: 866b44ead61c34eb7edb84b434e56cccbc42824dea462b04b91037c85aef7d60
| Timestamp: 1779436976 | Timestamp [UTC]: 2026-05-22 08:02:56 | Age [y:d:h:m:s]: 00:017:18:37:40 |
| Block: 155 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7742 | RingCT/type: yes/0 |
| Extra: 01866b44ead61c34eb7edb84b434e56cccbc42824dea462b04b91037c85aef7d60020900000001a662ed0300 | ||
1 output(s) for total of 35.174038831711 HMNY
| stealth address | amount | amount idx | tag |
| 00: 33b570ec688b7f20ea501599039993a72f1a70370da3ba43de2e695e18118da9 | 35.174038831711 | 151 of 0 | <5c> |
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": 215,
"vin": [ {
"gen": {
"height": 155
}
}
],
"vout": [ {
"amount": 35174038831711,
"target": {
"tagged_key": {
"key": "33b570ec688b7f20ea501599039993a72f1a70370da3ba43de2e695e18118da9",
"view_tag": "5c"
}
}
}
],
"extra": [ 1, 134, 107, 68, 234, 214, 28, 52, 235, 126, 219, 132, 180, 52, 229, 108, 204, 188, 66, 130, 77, 234, 70, 43, 4, 185, 16, 55, 200, 90, 239, 125, 96, 2, 9, 0, 0, 0, 1, 166, 98, 237, 3, 0
],
"rct_signatures": {
"type": 0
}
}