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: c45f9403a6582a9a8d6b945606040274e012f7ca3051d371275e16b470a33667
Tx prefix hash: 9077c77d7e87a6453c5d6e0a57621cfd8eb685a33155733a9f174ee4e413fcdf
Tx public key: d66bcfca8b44d897058a4dc4d02115b06872d58d06dc2bcde52931f583aec287
| Timestamp: 1779944807 | Timestamp [UTC]: 2026-05-28 05:06:47 | Age [y:d:h:m:s]: 00:011:19:40:00 |
| Block: 3548 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4338 | RingCT/type: yes/0 |
| Extra: 01d66bcfca8b44d897058a4dc4d02115b06872d58d06dc2bcde52931f583aec28702090000000226697be300 | ||
1 output(s) for total of 34.947140107484 HMNY
| stealth address | amount | amount idx | tag |
| 00: 676290d3c9d975f53a6efb732e32f6699b342c9f1def18ea00c33b533eedb46f | 34.947140107484 | 4278 of 0 | <12> |
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": 3608,
"vin": [ {
"gen": {
"height": 3548
}
}
],
"vout": [ {
"amount": 34947140107484,
"target": {
"tagged_key": {
"key": "676290d3c9d975f53a6efb732e32f6699b342c9f1def18ea00c33b533eedb46f",
"view_tag": "12"
}
}
}
],
"extra": [ 1, 214, 107, 207, 202, 139, 68, 216, 151, 5, 138, 77, 196, 208, 33, 21, 176, 104, 114, 213, 141, 6, 220, 43, 205, 229, 41, 49, 245, 131, 174, 194, 135, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}