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: a95f7ad850092afabc3fde864c5b4b64b579cddc2f0f63aa04ee59d730b05618
Tx prefix hash: 4d217a557d75f1e9747b9a348e3858e84be90e1c867441c54e3b1dd5216dd349
Tx public key: 3770c87ef2d381b7e52cbca0237e9ddb6f03445e6989200e8f3763b4e6d44e12
| Timestamp: 1780063248 | Timestamp [UTC]: 2026-05-29 14:00:48 | Age [y:d:h:m:s]: 00:010:10:45:59 |
| Block: 4551 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3335 | RingCT/type: yes/0 |
| Extra: 013770c87ef2d381b7e52cbca0237e9ddb6f03445e6989200e8f3763b4e6d44e1202090000000126697be300 | ||
1 output(s) for total of 34.880347604501 HMNY
| stealth address | amount | amount idx | tag |
| 00: 58a26cf0711de21aac012ba5d52d79bec6015862fe84ed599484bb25629da59f | 34.880347604501 | 5712 of 0 | <6b> |
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": 4611,
"vin": [ {
"gen": {
"height": 4551
}
}
],
"vout": [ {
"amount": 34880347604501,
"target": {
"tagged_key": {
"key": "58a26cf0711de21aac012ba5d52d79bec6015862fe84ed599484bb25629da59f",
"view_tag": "6b"
}
}
}
],
"extra": [ 1, 55, 112, 200, 126, 242, 211, 129, 183, 229, 44, 188, 160, 35, 126, 157, 219, 111, 3, 68, 94, 105, 137, 32, 14, 143, 55, 99, 180, 230, 212, 78, 18, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}