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: f06a371b353afaf04d090fe845f294866f3f27beee947d25ec1d950b44b110e2
Tx prefix hash: b1f058aef724de47471524e97c5d7be25cfd3cfb917e6bccb94fc6b1e8b60fd6
Tx public key: 32427565500541a0ba58e69daeabc82ef04b4eae7bbb434828afba79192860aa
| Timestamp: 1780983560 | Timestamp [UTC]: 2026-06-09 05:39:20 | Age [y:d:h:m:s]: 00:000:06:58:25 |
| Block: 8094 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 480 | RingCT/type: yes/0 |
| Extra: 0132427565500541a0ba58e69daeabc82ef04b4eae7bbb434828afba79192860aa020900000001e49593ff00 | ||
1 output(s) for total of 34.645429842711 HMNY
| stealth address | amount | amount idx | tag |
| 00: 43c86984a8e2e05521fda80be6704e3cd262da6d9db0782e2f11531380981903 | 34.645429842711 | 10026 of 0 | <2b> |
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": 8154,
"vin": [ {
"gen": {
"height": 8094
}
}
],
"vout": [ {
"amount": 34645429842711,
"target": {
"tagged_key": {
"key": "43c86984a8e2e05521fda80be6704e3cd262da6d9db0782e2f11531380981903",
"view_tag": "2b"
}
}
}
],
"extra": [ 1, 50, 66, 117, 101, 80, 5, 65, 160, 186, 88, 230, 157, 174, 171, 200, 46, 240, 75, 78, 174, 123, 187, 67, 72, 40, 175, 186, 121, 25, 40, 96, 170, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}