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: 84b5f0454db4f4ed58767247ac9bb6842d99a198d69fcb54db597974c91b23ce
Tx prefix hash: c4b7d82005e2b361dcb8ae282710aacf923b8760ea65ee6529df4a8e99a00f8a
Tx public key: e53ddae89c4ade6cbf54ec8b17c49e6e00e46c50734eabc910b6f7f4b5ec956a
| Timestamp: 1780816643 | Timestamp [UTC]: 2026-06-07 07:17:23 | Age [y:d:h:m:s]: 00:001:18:18:34 |
| Block: 7081 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 805 | RingCT/type: yes/0 |
| Extra: 01e53ddae89c4ade6cbf54ec8b17c49e6e00e46c50734eabc910b6f7f4b5ec956a020900000003e49593ff00 | ||
1 output(s) for total of 34.712434582291 HMNY
| stealth address | amount | amount idx | tag |
| 00: c1f0e8dcb7f960233029e3ed7880adb4f7d5e3ae787760bdfae706175a741f6b | 34.712434582291 | 8729 of 0 | <d2> |
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": 7141,
"vin": [ {
"gen": {
"height": 7081
}
}
],
"vout": [ {
"amount": 34712434582291,
"target": {
"tagged_key": {
"key": "c1f0e8dcb7f960233029e3ed7880adb4f7d5e3ae787760bdfae706175a741f6b",
"view_tag": "d2"
}
}
}
],
"extra": [ 1, 229, 61, 218, 232, 156, 74, 222, 108, 191, 84, 236, 139, 23, 196, 158, 110, 0, 228, 108, 80, 115, 78, 171, 201, 16, 182, 247, 244, 181, 236, 149, 106, 2, 9, 0, 0, 0, 3, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}