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: cb69deea07814b34c42d35710e5d05ca49e318df164529d54d4342b271b7c2d9
Tx prefix hash: 3ead5012770aff4fdf00a9f4a1a9614040e2ac3dc6266ecc37c2b743e2ce1e44
Tx public key: e342a5262418437e5b805e4f14bef00d7cdc26f529a047a5c86e16ccf1231ef3
| Timestamp: 1780754007 | Timestamp [UTC]: 2026-06-06 13:53:27 | Age [y:d:h:m:s]: 00:002:10:53:20 |
| Block: 6515 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1371 | RingCT/type: yes/0 |
| Extra: 01e342a5262418437e5b805e4f14bef00d7cdc26f529a047a5c86e16ccf1231ef3020900000001e49593ff00 | ||
1 output(s) for total of 34.749928985610 HMNY
| stealth address | amount | amount idx | tag |
| 00: eaaa0db316ac2add4d13b49681605d50ee43cf2c86bdf6f41c1f292a660198ff | 34.749928985610 | 8012 of 0 | <4d> |
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": 6575,
"vin": [ {
"gen": {
"height": 6515
}
}
],
"vout": [ {
"amount": 34749928985610,
"target": {
"tagged_key": {
"key": "eaaa0db316ac2add4d13b49681605d50ee43cf2c86bdf6f41c1f292a660198ff",
"view_tag": "4d"
}
}
}
],
"extra": [ 1, 227, 66, 165, 38, 36, 24, 67, 126, 91, 128, 94, 79, 20, 190, 240, 13, 124, 220, 38, 245, 41, 160, 71, 165, 200, 110, 22, 204, 241, 35, 30, 243, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}