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: 63e457c09ea2b025a47dafeb9f913034f1e89bc9a29e124a33733a6d28d5cf82
Tx prefix hash: 7c508fe94b0bb1828629ebee7f7b41229d370f31b3525592fc9f803f46255fe4
Tx public key: 16b75b0c6cdb9d3b1c7e405f34d728a6397e29d4f6f924e2db46d401af5df490
| Timestamp: 1780720181 | Timestamp [UTC]: 2026-06-06 04:29:41 | Age [y:d:h:m:s]: 00:002:18:49:12 |
| Block: 6235 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1651 | RingCT/type: yes/0 |
| Extra: 0116b75b0c6cdb9d3b1c7e405f34d728a6397e29d4f6f924e2db46d401af5df490020900000002e49593ff00 | ||
1 output(s) for total of 34.768492424117 HMNY
| stealth address | amount | amount idx | tag |
| 00: 18c17ef05c458ac701ec0dbe2c47bad5edf9d0c1cb5f79320b213db7be2dff39 | 34.768492424117 | 7716 of 0 | <a2> |
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": 6295,
"vin": [ {
"gen": {
"height": 6235
}
}
],
"vout": [ {
"amount": 34768492424117,
"target": {
"tagged_key": {
"key": "18c17ef05c458ac701ec0dbe2c47bad5edf9d0c1cb5f79320b213db7be2dff39",
"view_tag": "a2"
}
}
}
],
"extra": [ 1, 22, 183, 91, 12, 108, 219, 157, 59, 28, 126, 64, 95, 52, 215, 40, 166, 57, 126, 41, 212, 246, 249, 36, 226, 219, 70, 212, 1, 175, 93, 244, 144, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}