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: e0f9b2a796d93abf5b9f59bae4ca8f831f9b74c82770e037ab89a4079048a845
Tx prefix hash: df8906ecd270ae46286323e19c2d36752a69bc88aa17c13c30f1ea9b05945045
Tx public key: 331952c23eec8d38aac34042f20d51f6ed34c89b53b93c014d350f01101ff843
| Timestamp: 1780683988 | Timestamp [UTC]: 2026-06-05 18:26:28 | Age [y:d:h:m:s]: 00:003:06:20:19 |
| Block: 5338 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2548 | RingCT/type: yes/0 |
| Extra: 01331952c23eec8d38aac34042f20d51f6ed34c89b53b93c014d350f01101ff843020900000001e49593ff00 | ||
1 output(s) for total of 34.828028522213 HMNY
| stealth address | amount | amount idx | tag |
| 00: 0dd6abb72c8df84af850acf3e7276314eb5c14132c9c5fd649272fa50496150d | 34.828028522213 | 6769 of 0 | <53> |
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": 5398,
"vin": [ {
"gen": {
"height": 5338
}
}
],
"vout": [ {
"amount": 34828028522213,
"target": {
"tagged_key": {
"key": "0dd6abb72c8df84af850acf3e7276314eb5c14132c9c5fd649272fa50496150d",
"view_tag": "53"
}
}
}
],
"extra": [ 1, 51, 25, 82, 194, 62, 236, 141, 56, 170, 195, 64, 66, 242, 13, 81, 246, 237, 52, 200, 155, 83, 185, 60, 1, 77, 53, 15, 1, 16, 31, 248, 67, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}