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: ef5bb117a6f1011e9d8dbb9ad6c9ae42fdf09d32b5a3dcb4ed302c6d74112cab
Tx prefix hash: cd15811e9f8b90399ba9278a59ffbcf200cc87fddf0a65c480ba347f9f685d1b
Tx public key: 3913078dff954f1e04ba5c99c8efef240df79d1658e5d0bc9badcce766be2416
| Timestamp: 1779899045 | Timestamp [UTC]: 2026-05-27 16:24:05 | Age [y:d:h:m:s]: 00:012:12:08:57 |
| Block: 3124 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4903 | RingCT/type: yes/0 |
| Extra: 013913078dff954f1e04ba5c99c8efef240df79d1658e5d0bc9badcce766be241602090000000526697be300 | ||
1 output(s) for total of 34.975413870706 HMNY
| stealth address | amount | amount idx | tag |
| 00: b9737820990da569146b81b85b09017d914f78a7bcac3c9c0e60a6069a9e4907 | 34.975413870706 | 3732 of 0 | <59> |
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": 3184,
"vin": [ {
"gen": {
"height": 3124
}
}
],
"vout": [ {
"amount": 34975413870706,
"target": {
"tagged_key": {
"key": "b9737820990da569146b81b85b09017d914f78a7bcac3c9c0e60a6069a9e4907",
"view_tag": "59"
}
}
}
],
"extra": [ 1, 57, 19, 7, 141, 255, 149, 79, 30, 4, 186, 92, 153, 200, 239, 239, 36, 13, 247, 157, 22, 88, 229, 208, 188, 155, 173, 204, 231, 102, 190, 36, 22, 2, 9, 0, 0, 0, 5, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}