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: 311ba018c9853120015e3bae739f8538ec6d74e97f4c0b793f145fc05f3f53d9
Tx prefix hash: 24d833485ee2e930bbff55d339218e6cc72e97c34af03c4481f903a8632aeec1
Tx public key: 6ab57ce392e466d305c81db4c094263c87c6f4cc002d3ec4a7fa9d743689ce4e
| Timestamp: 1779965808 | Timestamp [UTC]: 2026-05-28 10:56:48 | Age [y:d:h:m:s]: 00:011:17:36:14 |
| Block: 3806 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4226 | RingCT/type: yes/0 |
| Extra: 016ab57ce392e466d305c81db4c094263c87c6f4cc002d3ec4a7fa9d743689ce4e02090000000726697be300 | ||
1 output(s) for total of 34.929946975754 HMNY
| stealth address | amount | amount idx | tag |
| 00: 79ef0e436fdbffbc64328ad60eb148151a00d5e2660f02d368c9253b7219b6c7 | 34.929946975754 | 4629 of 0 | <5f> |
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": 3866,
"vin": [ {
"gen": {
"height": 3806
}
}
],
"vout": [ {
"amount": 34929946975754,
"target": {
"tagged_key": {
"key": "79ef0e436fdbffbc64328ad60eb148151a00d5e2660f02d368c9253b7219b6c7",
"view_tag": "5f"
}
}
}
],
"extra": [ 1, 106, 181, 124, 227, 146, 228, 102, 211, 5, 200, 29, 180, 192, 148, 38, 60, 135, 198, 244, 204, 0, 45, 62, 196, 167, 250, 157, 116, 54, 137, 206, 78, 2, 9, 0, 0, 0, 7, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}