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: 621e65b018eaf929c79d21be8df4df5f9a9e709d46037523b6a978c898bc3873
Tx prefix hash: 97ee052f868a470b87276a8bf48d43cd1fb610c50a55341d1612be61c5329e03
Tx public key: a10514976b0c7840a5c6fff740aa099aa3580a29793b82a5d30378776ca9b024
| Timestamp: 1780710006 | Timestamp [UTC]: 2026-06-06 01:40:06 | Age [y:d:h:m:s]: 00:002:23:55:51 |
| Block: 6152 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1734 | RingCT/type: yes/0 |
| Extra: 01a10514976b0c7840a5c6fff740aa099aa3580a29793b82a5d30378776ca9b024020900000003e49593ff00 | ||
1 output(s) for total of 34.773997062903 HMNY
| stealth address | amount | amount idx | tag |
| 00: 97bf3407367f6bbdfa88db236c97d6011f87cdff82ce3943173044e1e47d1810 | 34.773997062903 | 7627 of 0 | <c6> |
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": 6212,
"vin": [ {
"gen": {
"height": 6152
}
}
],
"vout": [ {
"amount": 34773997062903,
"target": {
"tagged_key": {
"key": "97bf3407367f6bbdfa88db236c97d6011f87cdff82ce3943173044e1e47d1810",
"view_tag": "c6"
}
}
}
],
"extra": [ 1, 161, 5, 20, 151, 107, 12, 120, 64, 165, 198, 255, 247, 64, 170, 9, 154, 163, 88, 10, 41, 121, 59, 130, 165, 211, 3, 120, 119, 108, 169, 176, 36, 2, 9, 0, 0, 0, 3, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}