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: 3290b8bcb26912f5b37a286c9ae34ba2bf575296786ad2283015432e1712491d
Tx prefix hash: d1f0adce46f7ea12fb9515519a627c8d068e8b7e78f70c34a8f999aa3f1841e9
Tx public key: b7f268597aa7a63b00af5124c02d2dc4c1993d7b27a08c2e613e1932a8778c30
| Timestamp: 1779847028 | Timestamp [UTC]: 2026-05-27 01:57:08 | Age [y:d:h:m:s]: 00:012:23:38:49 |
| Block: 2473 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5413 | RingCT/type: yes/0 |
| Extra: 01b7f268597aa7a63b00af5124c02d2dc4c1993d7b27a08c2e613e1932a8778c3002090000000126697be300 | ||
1 output(s) for total of 35.018869295914 HMNY
| stealth address | amount | amount idx | tag |
| 00: e05f9dd0cfba2375404e6cc06d6b4d79fa26b72d9bcb2c5c769995aa5fd5682a | 35.018869295914 | 2907 of 0 | <1f> |
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": 2533,
"vin": [ {
"gen": {
"height": 2473
}
}
],
"vout": [ {
"amount": 35018869295914,
"target": {
"tagged_key": {
"key": "e05f9dd0cfba2375404e6cc06d6b4d79fa26b72d9bcb2c5c769995aa5fd5682a",
"view_tag": "1f"
}
}
}
],
"extra": [ 1, 183, 242, 104, 89, 122, 167, 166, 59, 0, 175, 81, 36, 192, 45, 45, 196, 193, 153, 61, 123, 39, 160, 140, 46, 97, 62, 25, 50, 168, 119, 140, 48, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}