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: 6903eebcd21c91c8cb54758df3b1351e12094b71c9da6a0b82358349871c49b3
Tx prefix hash: efc9739547a3fc367eee3dd789516a79c8ee8dbc211301f7d709f9765f7e4d06
Tx public key: 6b647ecc3650932f53816dc7eda0baa3aff448f3e5c0c14a4b91835fd1c0d0e1
| Timestamp: 1780888759 | Timestamp [UTC]: 2026-06-08 03:19:19 | Age [y:d:h:m:s]: 00:000:19:59:34 |
| Block: 7705 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 181 | RingCT/type: yes/0 |
| Extra: 016b647ecc3650932f53816dc7eda0baa3aff448f3e5c0c14a4b91835fd1c0d0e1020900000001e49593ff00 | ||
1 output(s) for total of 34.671144881054 HMNY
| stealth address | amount | amount idx | tag |
| 00: 2d1128bafb28a1a3d8ff82b94c44fcbb012ea06e1d9c933f028cd64170694da4 | 34.671144881054 | 9533 of 0 | <1f> |
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": 7765,
"vin": [ {
"gen": {
"height": 7705
}
}
],
"vout": [ {
"amount": 34671144881054,
"target": {
"tagged_key": {
"key": "2d1128bafb28a1a3d8ff82b94c44fcbb012ea06e1d9c933f028cd64170694da4",
"view_tag": "1f"
}
}
}
],
"extra": [ 1, 107, 100, 126, 204, 54, 80, 147, 47, 83, 129, 109, 199, 237, 160, 186, 163, 175, 244, 72, 243, 229, 192, 193, 74, 75, 145, 131, 95, 209, 192, 208, 225, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}