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: 56b6bca244784be0147213f6f6921bc2571899e805bc22b2c565b84ddd98a0da
Tx prefix hash: 188c10d5b8f9460cc65e5f33c646d54db51442ed5c25263241a5e7a0d297e382
Tx public key: 3b054afd4dc3a93b4482a190223e83aa995d3c3ab3b4559263f95d7e3e5be7ff
| Timestamp: 1779629377 | Timestamp [UTC]: 2026-05-24 13:29:37 | Age [y:d:h:m:s]: 00:015:11:17:10 |
| Block: 827 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7059 | RingCT/type: yes/0 |
| Extra: 013b054afd4dc3a93b4482a190223e83aa995d3c3ab3b4559263f95d7e3e5be7ff020900000001ba6d17be00 | ||
1 output(s) for total of 35.128983757242 HMNY
| stealth address | amount | amount idx | tag |
| 00: 9bea3f775cc5eaffbb35ab620794681b2ca709c880fcacd016ef7f022c26bedc | 35.128983757242 | 959 of 0 | <01> |
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": 887,
"vin": [ {
"gen": {
"height": 827
}
}
],
"vout": [ {
"amount": 35128983757242,
"target": {
"tagged_key": {
"key": "9bea3f775cc5eaffbb35ab620794681b2ca709c880fcacd016ef7f022c26bedc",
"view_tag": "01"
}
}
}
],
"extra": [ 1, 59, 5, 74, 253, 77, 195, 169, 59, 68, 130, 161, 144, 34, 62, 131, 170, 153, 93, 60, 58, 179, 180, 85, 146, 99, 249, 93, 126, 62, 91, 231, 255, 2, 9, 0, 0, 0, 1, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}