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: 99a5369b583741df1acc4f4dca1da9dcea405cf465749e8d24eaf10228d30411
Tx prefix hash: 1b9fc721d12e86e5886fdec88069aa8a8ae4db397798e41649e694463951bb58
Tx public key: 1e46c150afbf434fd6667287e56b52c2f241dafa03b49f6526c5d2ae58b57f70
| Timestamp: 1780037885 | Timestamp [UTC]: 2026-05-29 06:58:05 | Age [y:d:h:m:s]: 00:010:18:37:52 |
| Block: 4257 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3629 | RingCT/type: yes/0 |
| Extra: 011e46c150afbf434fd6667287e56b52c2f241dafa03b49f6526c5d2ae58b57f7002090000000a26697be300 | ||
1 output(s) for total of 34.899912629388 HMNY
| stealth address | amount | amount idx | tag |
| 00: 7ad9246dbada7e3c53738f04920399d9dd43fcc5e6b4ec25792e1b47260c0fd9 | 34.899912629388 | 5314 of 0 | <06> |
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": 4317,
"vin": [ {
"gen": {
"height": 4257
}
}
],
"vout": [ {
"amount": 34899912629388,
"target": {
"tagged_key": {
"key": "7ad9246dbada7e3c53738f04920399d9dd43fcc5e6b4ec25792e1b47260c0fd9",
"view_tag": "06"
}
}
}
],
"extra": [ 1, 30, 70, 193, 80, 175, 191, 67, 79, 214, 102, 114, 135, 229, 107, 82, 194, 242, 65, 218, 250, 3, 180, 159, 101, 38, 197, 210, 174, 88, 181, 127, 112, 2, 9, 0, 0, 0, 10, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}