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: 9078cda1fe121468dd986789c58210d98b5e77fc486086994bbd8c4fcb2dd0a7
Tx prefix hash: 0bb6ccae52fb6c4b80ef3bfa391b0de48abbd39c137a92e56d16056d14aee43a
Tx public key: c753a1691b8481ee07e127395e806ccd1ba6d6a786a84b35d6bb7faaaa489531
| Timestamp: 1780023077 | Timestamp [UTC]: 2026-05-29 02:51:17 | Age [y:d:h:m:s]: 00:010:22:44:40 |
| Block: 4153 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3733 | RingCT/type: yes/0 |
| Extra: 01c753a1691b8481ee07e127395e806ccd1ba6d6a786a84b35d6bb7faaaa48953102090000000326697be300 | ||
1 output(s) for total of 34.906836217931 HMNY
| stealth address | amount | amount idx | tag |
| 00: 14d8e60ccb40f29fd1c64eef2d100b947c707e1b6714e0a5a482c89d516a55a7 | 34.906836217931 | 5184 of 0 | <04> |
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": 4213,
"vin": [ {
"gen": {
"height": 4153
}
}
],
"vout": [ {
"amount": 34906836217931,
"target": {
"tagged_key": {
"key": "14d8e60ccb40f29fd1c64eef2d100b947c707e1b6714e0a5a482c89d516a55a7",
"view_tag": "04"
}
}
}
],
"extra": [ 1, 199, 83, 161, 105, 27, 132, 129, 238, 7, 225, 39, 57, 94, 128, 108, 205, 27, 166, 214, 167, 134, 168, 75, 53, 214, 187, 127, 170, 170, 72, 149, 49, 2, 9, 0, 0, 0, 3, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}