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: 4aea22f325e094dec8c19f8938d7ff709d0c02804ea86a11be34babd8228fd44
Tx prefix hash: 0f27eb28c1e6136e980e2148375c80b036a2107f9fb398b7224553c34f98822a
Tx public key: a8c3d269301c3efd53965425939edbdb59d997ff77d51451491bfcd99246cc48
| Timestamp: 1780071112 | Timestamp [UTC]: 2026-05-29 16:11:52 | Age [y:d:h:m:s]: 00:014:18:50:24 |
| Block: 4645 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4100 | RingCT/type: yes/0 |
| Extra: 01a8c3d269301c3efd53965425939edbdb59d997ff77d51451491bfcd99246cc4802090000000726697be300 | ||
1 output(s) for total of 34.874094434691 HMNY
| stealth address | amount | amount idx | tag |
| 00: 83c5aa65c38d037b1cc3b548328dfd04b8760696e2d67c60a981702c79805caf | 34.874094434691 | 5834 of 0 | <c3> |
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": 4705,
"vin": [ {
"gen": {
"height": 4645
}
}
],
"vout": [ {
"amount": 34874094434691,
"target": {
"tagged_key": {
"key": "83c5aa65c38d037b1cc3b548328dfd04b8760696e2d67c60a981702c79805caf",
"view_tag": "c3"
}
}
}
],
"extra": [ 1, 168, 195, 210, 105, 48, 28, 62, 253, 83, 150, 84, 37, 147, 158, 219, 219, 89, 217, 151, 255, 119, 213, 20, 81, 73, 27, 252, 217, 146, 70, 204, 72, 2, 9, 0, 0, 0, 7, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}