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: 4d06bb37c53acb03547f9072215351bec01ee85dc0c54b83931e22187447ec32
Tx prefix hash: 20fb25e374866f5929bb2ee3f48f3677e0adda19f3212382c40bc5332de8d3ff
Tx public key: b23c7557e403ec22dbe9743ce24fd17fce82e9e392515e89c533d95ddb608783
| Timestamp: 1780072923 | Timestamp [UTC]: 2026-05-29 16:42:03 | Age [y:d:h:m:s]: 00:010:04:30:04 |
| Block: 4666 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3220 | RingCT/type: yes/0 |
| Extra: 01b23c7557e403ec22dbe9743ce24fd17fce82e9e392515e89c533d95ddb60878302090000000126697be300 | ||
1 output(s) for total of 34.872697603150 HMNY
| stealth address | amount | amount idx | tag |
| 00: c6536e080b7a5972ae50aafacdab9e3ae322819ba4406021b00959832df4ad09 | 34.872697603150 | 5861 of 0 | <3c> |
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": 4726,
"vin": [ {
"gen": {
"height": 4666
}
}
],
"vout": [ {
"amount": 34872697603150,
"target": {
"tagged_key": {
"key": "c6536e080b7a5972ae50aafacdab9e3ae322819ba4406021b00959832df4ad09",
"view_tag": "3c"
}
}
}
],
"extra": [ 1, 178, 60, 117, 87, 228, 3, 236, 34, 219, 233, 116, 60, 226, 79, 209, 127, 206, 130, 233, 227, 146, 81, 94, 137, 197, 51, 217, 93, 219, 96, 135, 131, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}