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: ea0d1ff8b68dba7f2a201c56f96e8353de77b64233f35ed29b89573422dfabf1
Tx prefix hash: 4eb74e64f95b759c5c62606104f3fa068e5eeccf08772fdafd5652eb762cce75
Tx public key: 547a8aa091dea019e5b976daa26bfcd9ee732d17b560dfcb0dd54f46208648cb
| Timestamp: 1781005971 | Timestamp [UTC]: 2026-06-09 11:52:51 | Age [y:d:h:m:s]: 00:006:06:21:51 |
| Block: 8544 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 201 | RingCT/type: yes/0 |
| Extra: 01547a8aa091dea019e5b976daa26bfcd9ee732d17b560dfcb0dd54f46208648cb020900000001e49593ff00 | ||
1 output(s) for total of 34.615706161249 HMNY
| stealth address | amount | amount idx | tag |
| 00: 25b2dc74d08fb5205e2755b3ac606069f027749649009ef4bdc6f9f3856dc586 | 34.615706161249 | 10552 of 0 | <5f> |
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": 8604,
"vin": [ {
"gen": {
"height": 8544
}
}
],
"vout": [ {
"amount": 34615706161249,
"target": {
"tagged_key": {
"key": "25b2dc74d08fb5205e2755b3ac606069f027749649009ef4bdc6f9f3856dc586",
"view_tag": "5f"
}
}
}
],
"extra": [ 1, 84, 122, 138, 160, 145, 222, 160, 25, 229, 185, 118, 218, 162, 107, 252, 217, 238, 115, 45, 23, 181, 96, 223, 203, 13, 213, 79, 70, 32, 134, 72, 203, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}