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: 323fbbde96b246f379afba2fb86e81f46e20c5880fddc2527052fef9ba070ea1
Tx prefix hash: 33560d577b8b81fcfc235f7f56f7219813bb380aaf8ce1286f7f33a4b3cb1523
Tx public key: d0312da15f2dbde620702dc4b61fa59e89e14c24802d728b8c46460f5a3bdb25
| Timestamp: 1779843483 | Timestamp [UTC]: 2026-05-27 00:58:03 | Age [y:d:h:m:s]: 00:013:01:51:45 |
| Block: 2424 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5496 | RingCT/type: yes/0 |
| Extra: 01d0312da15f2dbde620702dc4b61fa59e89e14c24802d728b8c46460f5a3bdb2502090000000326697be300 | ||
1 output(s) for total of 35.022142318412 HMNY
| stealth address | amount | amount idx | tag |
| 00: 93fc0debda96776ffa710e0c01dc881b948676cc1cfe91bdbcfcfc40c5edc439 | 35.022142318412 | 2846 of 0 | <7f> |
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": 2484,
"vin": [ {
"gen": {
"height": 2424
}
}
],
"vout": [ {
"amount": 35022142318412,
"target": {
"tagged_key": {
"key": "93fc0debda96776ffa710e0c01dc881b948676cc1cfe91bdbcfcfc40c5edc439",
"view_tag": "7f"
}
}
}
],
"extra": [ 1, 208, 49, 45, 161, 95, 45, 189, 230, 32, 112, 45, 196, 182, 31, 165, 158, 137, 225, 76, 36, 128, 45, 114, 139, 140, 70, 70, 15, 90, 59, 219, 37, 2, 9, 0, 0, 0, 3, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}