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: 01c1ab739daf9f0fb17adfb524404781c6917061d09ef72594105e8c9770f5d0
Tx prefix hash: 588574a3e27010cb2056a5b64858d1e2804bc59e885938dd226834445f6c4d08
Tx public key: f5b78a79f0f9e2918e39c2d3f969f9b8ad5d4fe9dc3b94a1f6027a2ef0c01ae9
| Timestamp: 1780994723 | Timestamp [UTC]: 2026-06-09 08:45:23 | Age [y:d:h:m:s]: 00:004:02:16:53 |
| Block: 8308 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 437 | RingCT/type: yes/0 |
| Extra: 01f5b78a79f0f9e2918e39c2d3f969f9b8ad5d4fe9dc3b94a1f6027a2ef0c01ae9020900000001e49593ff00 | ||
1 output(s) for total of 34.631291399452 HMNY
| stealth address | amount | amount idx | tag |
| 00: 5aa229f7575731cfb307cc6cfdcf6fa58c1acb209d4ade2f5532e0ad6577069a | 34.631291399452 | 10278 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": 8368,
"vin": [ {
"gen": {
"height": 8308
}
}
],
"vout": [ {
"amount": 34631291399452,
"target": {
"tagged_key": {
"key": "5aa229f7575731cfb307cc6cfdcf6fa58c1acb209d4ade2f5532e0ad6577069a",
"view_tag": "12"
}
}
}
],
"extra": [ 1, 245, 183, 138, 121, 240, 249, 226, 145, 142, 57, 194, 211, 249, 105, 249, 184, 173, 93, 79, 233, 220, 59, 148, 161, 246, 2, 122, 46, 240, 192, 26, 233, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}