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: c48a88546d3b4e1ffde97151f1371ccc6ce21f2deb937eb3bb59f7a05da23f93
Tx prefix hash: 6411e5c27dc6fa5685a833021e20915c4ff8c15fd1b66e9b90e0e28565144c86
Tx public key: 70ff3a899750e37457f8f854823eddf23995569c64fcd4b79e44b0c9bc37c6a4
| Timestamp: 1779441686 | Timestamp [UTC]: 2026-05-22 09:21:26 | Age [y:d:h:m:s]: 00:018:07:47:37 |
| Block: 222 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 8512 | RingCT/type: yes/0 |
| Extra: 0170ff3a899750e37457f8f854823eddf23995569c64fcd4b79e44b0c9bc37c6a4020900000001c3b6d28a00 | ||
1 output(s) for total of 35.169544141248 HMNY
| stealth address | amount | amount idx | tag |
| 00: 4009fede8ec709d468df8c91c3287f104fb16de707b90ba2d16413a810ce1452 | 35.169544141248 | 218 of 0 | <60> |
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": 282,
"vin": [ {
"gen": {
"height": 222
}
}
],
"vout": [ {
"amount": 35169544141248,
"target": {
"tagged_key": {
"key": "4009fede8ec709d468df8c91c3287f104fb16de707b90ba2d16413a810ce1452",
"view_tag": "60"
}
}
}
],
"extra": [ 1, 112, 255, 58, 137, 151, 80, 227, 116, 87, 248, 248, 84, 130, 62, 221, 242, 57, 149, 86, 156, 100, 252, 212, 183, 158, 68, 176, 201, 188, 55, 198, 164, 2, 9, 0, 0, 0, 1, 195, 182, 210, 138, 0
],
"rct_signatures": {
"type": 0
}
}