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: cf5c73a2d9ce33f793807262d73dc1d3d490519af711422f9133b03c06b6bf42
Tx prefix hash: 48ce0e64d4b53962690ae470974b6e8e18d0974b6b0c6a5cb689c14e83a470c9
Tx public key: 1eed460898da7db1d3a589b4f88f1afe66b5bb92b15d3ab5bf8ac179ca243313
| Timestamp: 1779461070 | Timestamp [UTC]: 2026-05-22 14:44:30 | Age [y:d:h:m:s]: 00:017:12:05:18 |
| Block: 437 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7483 | RingCT/type: yes/0 |
| Extra: 011eed460898da7db1d3a589b4f88f1afe66b5bb92b15d3ab5bf8ac179ca24331302090000000293369e7d00 | ||
1 output(s) for total of 35.155124759133 HMNY
| stealth address | amount | amount idx | tag |
| 00: d3ab08a0653ebb959c5f8c81060a6aae5d4a4ebf5dc72be55f407b73a9baedca | 35.155124759133 | 441 of 0 | <6e> |
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": 497,
"vin": [ {
"gen": {
"height": 437
}
}
],
"vout": [ {
"amount": 35155124759133,
"target": {
"tagged_key": {
"key": "d3ab08a0653ebb959c5f8c81060a6aae5d4a4ebf5dc72be55f407b73a9baedca",
"view_tag": "6e"
}
}
}
],
"extra": [ 1, 30, 237, 70, 8, 152, 218, 125, 177, 211, 165, 137, 180, 248, 143, 26, 254, 102, 181, 187, 146, 177, 93, 58, 181, 191, 138, 193, 121, 202, 36, 51, 19, 2, 9, 0, 0, 0, 2, 147, 54, 158, 125, 0
],
"rct_signatures": {
"type": 0
}
}