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: 0d6d8ee7e58f6c0cf834325ae7fee29106fb2c27042ea5805f19ad2403fc19ae
Tx prefix hash: 7e21ea77e897a0e77b8d71ac2d8f04d2b1fc5b3957766d411263d69d351bc5de
Tx public key: 178bca730b8ef44d33f521345496f2a91ba0bac3bf71d756094a0bd0aa5bf3ea
| Timestamp: 1780052158 | Timestamp [UTC]: 2026-05-29 10:55:58 | Age [y:d:h:m:s]: 00:010:13:50:49 |
| Block: 4411 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3475 | RingCT/type: yes/0 |
| Extra: 01178bca730b8ef44d33f521345496f2a91ba0bac3bf71d756094a0bd0aa5bf3ea02090000000126697be300 | ||
1 output(s) for total of 34.889662914722 HMNY
| stealth address | amount | amount idx | tag |
| 00: 69c6f2a59439e778ed5999d818de1999df7223c6c9de59e3c4a7e37b4b879e83 | 34.889662914722 | 5519 of 0 | <f4> |
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": 4471,
"vin": [ {
"gen": {
"height": 4411
}
}
],
"vout": [ {
"amount": 34889662914722,
"target": {
"tagged_key": {
"key": "69c6f2a59439e778ed5999d818de1999df7223c6c9de59e3c4a7e37b4b879e83",
"view_tag": "f4"
}
}
}
],
"extra": [ 1, 23, 139, 202, 115, 11, 142, 244, 77, 51, 245, 33, 52, 84, 150, 242, 169, 27, 160, 186, 195, 191, 113, 215, 86, 9, 74, 11, 208, 170, 91, 243, 234, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}