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: 26b57546940e5b6f49f251a885956a328bf49e8bd7d3c529dfb029eec1ad73ff
Tx prefix hash: e80b5d7980d1f1632262133140f56e68f5fff5be641cc531d106df355a755639
Tx public key: f15c729a188b617b43b0af98089eec1b8d5ff84e2ce0dc7d7bb0d70f765a6deb
| Timestamp: 1780741101 | Timestamp [UTC]: 2026-06-06 10:18:21 | Age [y:d:h:m:s]: 00:002:14:28:26 |
| Block: 6408 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1478 | RingCT/type: yes/0 |
| Extra: 01f15c729a188b617b43b0af98089eec1b8d5ff84e2ce0dc7d7bb0d70f765a6deb020900000002e49593ff00 | ||
1 output(s) for total of 34.757021700674 HMNY
| stealth address | amount | amount idx | tag |
| 00: abf7db9143d09e72bedf48b881a329a6bb1e057caef567ad5aef082edef2a815 | 34.757021700674 | 7899 of 0 | <a4> |
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": 6468,
"vin": [ {
"gen": {
"height": 6408
}
}
],
"vout": [ {
"amount": 34757021700674,
"target": {
"tagged_key": {
"key": "abf7db9143d09e72bedf48b881a329a6bb1e057caef567ad5aef082edef2a815",
"view_tag": "a4"
}
}
}
],
"extra": [ 1, 241, 92, 114, 154, 24, 139, 97, 123, 67, 176, 175, 152, 8, 158, 236, 27, 141, 95, 248, 78, 44, 224, 220, 125, 123, 176, 215, 15, 118, 90, 109, 235, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}