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: 34a206632f2be8cfc83b4ac23b8199a1f9a0b918744e312a2868539a06e3e6f0
Tx prefix hash: b330bc670e25a8c9e7fc6b59de7ddeddafd1663a25330173ff3e9ee207f39874
Tx public key: b40748db8c8ed9c3cee3d0653ba34f63b3a5d4107a4287fe69d5de3adb7f6d89
| Timestamp: 1780323027 | Timestamp [UTC]: 2026-06-01 14:10:27 | Age [y:d:h:m:s]: 00:007:09:08:26 |
| Block: 5043 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2843 | RingCT/type: yes/0 |
| Extra: 01b40748db8c8ed9c3cee3d0653ba34f63b3a5d4107a4287fe69d5de3adb7f6d8902090000000b26697be300 | ||
1 output(s) for total of 34.847630666951 HMNY
| stealth address | amount | amount idx | tag |
| 00: 106a4c5673ef9d28dc2c191d20ac23d0404a27f7831eafab3a6ffc2ffd2e69f7 | 34.847630666951 | 6418 of 0 | <40> |
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": 5103,
"vin": [ {
"gen": {
"height": 5043
}
}
],
"vout": [ {
"amount": 34847630666951,
"target": {
"tagged_key": {
"key": "106a4c5673ef9d28dc2c191d20ac23d0404a27f7831eafab3a6ffc2ffd2e69f7",
"view_tag": "40"
}
}
}
],
"extra": [ 1, 180, 7, 72, 219, 140, 142, 217, 195, 206, 227, 208, 101, 59, 163, 79, 99, 179, 165, 212, 16, 122, 66, 135, 254, 105, 213, 222, 58, 219, 127, 109, 137, 2, 9, 0, 0, 0, 11, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}