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: de71cd5f17154af470daeb951083e90cdcc0ee1e0a2fca4ef1d9ba9424c1bfc6
Tx prefix hash: 6801efcc72ece2eaef1244e1ceeead40769dc28a3a3f731f370399b1255e1ebe
Tx public key: 7519e43f58cced3cd8ceaf2b482bb73cceed65ddf8bdf85d50e3cc56229dbd33
| Timestamp: 1780981225 | Timestamp [UTC]: 2026-06-09 05:00:25 | Age [y:d:h:m:s]: 00:000:09:48:30 |
| Block: 8033 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 606 | RingCT/type: yes/0 |
| Extra: 017519e43f58cced3cd8ceaf2b482bb73cceed65ddf8bdf85d50e3cc56229dbd33020900000001e49593ff00 | ||
1 output(s) for total of 34.659287816769 HMNY
| stealth address | amount | amount idx | tag |
| 00: abbb64a2e0e4205ed1b67c28ec4e4ec8713778c11fb634e4d97e49fcb8b51dd7 | 34.659287816769 | 9957 of 0 | <42> |
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": 8093,
"vin": [ {
"gen": {
"height": 8033
}
}
],
"vout": [ {
"amount": 34659287816769,
"target": {
"tagged_key": {
"key": "abbb64a2e0e4205ed1b67c28ec4e4ec8713778c11fb634e4d97e49fcb8b51dd7",
"view_tag": "42"
}
}
}
],
"extra": [ 1, 117, 25, 228, 63, 88, 204, 237, 60, 216, 206, 175, 43, 72, 43, 183, 60, 206, 237, 101, 221, 248, 189, 248, 93, 80, 227, 204, 86, 34, 157, 189, 51, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}