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: 30267b1e739ce60e81b7d8d1927183f02e5f5f90d59e58d34a8df705f05ebefa
Tx prefix hash: 37759144319f0d014e206441d39bc3d13abcbcc5fb519bbdca277d6b8b92696d
Tx public key: b8e9d22eace5841f1e046ac013d9284f6f0674c9d29b9d0e9aa5f9247ba9fd83
| Timestamp: 1780688331 | Timestamp [UTC]: 2026-06-05 19:38:51 | Age [y:d:h:m:s]: 00:003:07:01:45 |
| Block: 5522 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2374 | RingCT/type: yes/0 |
| Extra: 01b8e9d22eace5841f1e046ac013d9284f6f0674c9d29b9d0e9aa5f9247ba9fd83020900000001e49593ff00 | ||
1 output(s) for total of 34.815807683713 HMNY
| stealth address | amount | amount idx | tag |
| 00: c9b46bb6d9f8a4e1fca91325139471bd41512303d2c38ce81188a9805f40aef1 | 34.815807683713 | 6963 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": 5582,
"vin": [ {
"gen": {
"height": 5522
}
}
],
"vout": [ {
"amount": 34815807683713,
"target": {
"tagged_key": {
"key": "c9b46bb6d9f8a4e1fca91325139471bd41512303d2c38ce81188a9805f40aef1",
"view_tag": "7f"
}
}
}
],
"extra": [ 1, 184, 233, 210, 46, 172, 229, 132, 31, 30, 4, 106, 192, 19, 217, 40, 79, 111, 6, 116, 201, 210, 155, 157, 14, 154, 165, 249, 36, 123, 169, 253, 131, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}