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: da2f35aca312ef9ff99c1f9124a05a3bec4b053216e17541b370147a5e85c0f3
Tx prefix hash: 705a8e6d06b0536e71d4351e5353cd1e96be2faf04bebc3b94c085ffa6cb9033
Tx public key: 1acf2a627b945be25701fbd0afb00a5b62917deb6e6e4cb5eda45c8da582eb9f
| Timestamp: 1780686023 | Timestamp [UTC]: 2026-06-05 19:00:23 | Age [y:d:h:m:s]: 00:003:06:35:34 |
| Block: 5409 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2477 | RingCT/type: yes/0 |
| Extra: 011acf2a627b945be25701fbd0afb00a5b62917deb6e6e4cb5eda45c8da582eb9f020900000002e49593ff00 | ||
1 output(s) for total of 34.823312364384 HMNY
| stealth address | amount | amount idx | tag |
| 00: 3ed975d18601702b4f0afd7e8d8ee7c41fd39cff6a67833e3470b07e21c38775 | 34.823312364384 | 6846 of 0 | <36> |
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": 5469,
"vin": [ {
"gen": {
"height": 5409
}
}
],
"vout": [ {
"amount": 34823312364384,
"target": {
"tagged_key": {
"key": "3ed975d18601702b4f0afd7e8d8ee7c41fd39cff6a67833e3470b07e21c38775",
"view_tag": "36"
}
}
}
],
"extra": [ 1, 26, 207, 42, 98, 123, 148, 91, 226, 87, 1, 251, 208, 175, 176, 10, 91, 98, 145, 125, 235, 110, 110, 76, 181, 237, 164, 92, 141, 165, 130, 235, 159, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}