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: 0b63e9cafbe16b7710c467a6b8e6a04dc29f66342eb95a1ffabf628bdcee1257
Tx prefix hash: 87525af6b49282fafefae1ee0d399cf59f64ebd2149eae24469f316ce4158d0b
Tx public key: 05af1117139e7bfed88250515446cab18572afbf12a3c59cd5bfa48b348e1178
| Timestamp: 1779936305 | Timestamp [UTC]: 2026-05-28 02:45:05 | Age [y:d:h:m:s]: 00:011:22:01:42 |
| Block: 3443 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4443 | RingCT/type: yes/0 |
| Extra: 0105af1117139e7bfed88250515446cab18572afbf12a3c59cd5bfa48b348e117802090000000826697be300 | ||
1 output(s) for total of 34.954139734939 HMNY
| stealth address | amount | amount idx | tag |
| 00: 2b934bfb78ad9c66cb89be3ace386dfb128585cabb39957d61101a8ca39a5fca | 34.954139734939 | 4160 of 0 | <ee> |
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": 3503,
"vin": [ {
"gen": {
"height": 3443
}
}
],
"vout": [ {
"amount": 34954139734939,
"target": {
"tagged_key": {
"key": "2b934bfb78ad9c66cb89be3ace386dfb128585cabb39957d61101a8ca39a5fca",
"view_tag": "ee"
}
}
}
],
"extra": [ 1, 5, 175, 17, 23, 19, 158, 123, 254, 216, 130, 80, 81, 84, 70, 202, 177, 133, 114, 175, 191, 18, 163, 197, 156, 213, 191, 164, 139, 52, 142, 17, 120, 2, 9, 0, 0, 0, 8, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}