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: bbf4d7d150905f73bb70e5b8207b9fc8b418b31dcd9f00d68d69f60aee1f2ff2
Tx prefix hash: 3b90164ff24c5abfae0b44995a35da85108151636f6ff0bc83fc44d233dc662c
Tx public key: 65d10c96fc0bea7ae3b392c54f2058ccf2719c7b311c42abf273d347c25c2a4b
| Timestamp: 1779645087 | Timestamp [UTC]: 2026-05-24 17:51:27 | Age [y:d:h:m:s]: 00:015:23:17:36 |
| Block: 1440 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7294 | RingCT/type: yes/0 |
| Extra: 0165d10c96fc0bea7ae3b392c54f2058ccf2719c7b311c42abf273d347c25c2a4b020900000001ba6d17be00 | ||
1 output(s) for total of 35.087934746785 HMNY
| stealth address | amount | amount idx | tag |
| 00: ee027686484131927a9b7818dda0e414ad149f6147b252079bed16a2ea0b8daa | 35.087934746785 | 1594 of 0 | <d0> |
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": 1500,
"vin": [ {
"gen": {
"height": 1440
}
}
],
"vout": [ {
"amount": 35087934746785,
"target": {
"tagged_key": {
"key": "ee027686484131927a9b7818dda0e414ad149f6147b252079bed16a2ea0b8daa",
"view_tag": "d0"
}
}
}
],
"extra": [ 1, 101, 209, 12, 150, 252, 11, 234, 122, 227, 179, 146, 197, 79, 32, 88, 204, 242, 113, 156, 123, 49, 28, 66, 171, 242, 115, 211, 71, 194, 92, 42, 75, 2, 9, 0, 0, 0, 1, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}