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: d2f19c2a3968ed118a4c71ad669c9ae674d5073289c1cc2d2b7ff89389e48cbe
Tx prefix hash: 5d2dad718a62247b7d23f24b75299eadb1b0403ccceda78985f07ba3f09a62b0
Tx public key: ebdac2a2c24e9ca1fbe29d279d1a413faf0b54082111d0463413ba417d74739b
| Timestamp: 1780763464 | Timestamp [UTC]: 2026-06-06 16:31:04 | Age [y:d:h:m:s]: 00:002:08:15:43 |
| Block: 6597 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1289 | RingCT/type: yes/0 |
| Extra: 01ebdac2a2c24e9ca1fbe29d279d1a413faf0b54082111d0463413ba417d74739b020900000002e49593ff00 | ||
1 output(s) for total of 34.744494426606 HMNY
| stealth address | amount | amount idx | tag |
| 00: 3ce4d1faab625c1e5750b6e871a10cab5dbe6d5b20beddbc3d5dc62543948afc | 34.744494426606 | 8127 of 0 | <e0> |
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": 6657,
"vin": [ {
"gen": {
"height": 6597
}
}
],
"vout": [ {
"amount": 34744494426606,
"target": {
"tagged_key": {
"key": "3ce4d1faab625c1e5750b6e871a10cab5dbe6d5b20beddbc3d5dc62543948afc",
"view_tag": "e0"
}
}
}
],
"extra": [ 1, 235, 218, 194, 162, 194, 78, 156, 161, 251, 226, 157, 39, 157, 26, 65, 63, 175, 11, 84, 8, 33, 17, 208, 70, 52, 19, 186, 65, 125, 116, 115, 155, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}