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: 8e5d099cc1eb7423039cfd67a7c807e3e05e5ac161cbed1f16050f7662c1e1b8
Tx prefix hash: 45a22775fe84eebbefd83b613c211eb64a784be4b2a5df5762340310dccb9701
Tx public key: 547d32c029c18561f9e69fbf5c30716ff581b01d2fea9cd211d115196558f08b
| Timestamp: 1779870739 | Timestamp [UTC]: 2026-05-27 08:32:19 | Age [y:d:h:m:s]: 00:012:17:03:38 |
| Block: 2800 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5086 | RingCT/type: yes/0 |
| Extra: 01547d32c029c18561f9e69fbf5c30716ff581b01d2fea9cd211d115196558f08b02090000000226697be300 | ||
1 output(s) for total of 34.997034711007 HMNY
| stealth address | amount | amount idx | tag |
| 00: 2fe7d132f901560817c711c57300c38474bb10bee05c64cf440331f35e8009f5 | 34.997034711007 | 3314 of 0 | <86> |
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": 2860,
"vin": [ {
"gen": {
"height": 2800
}
}
],
"vout": [ {
"amount": 34997034711007,
"target": {
"tagged_key": {
"key": "2fe7d132f901560817c711c57300c38474bb10bee05c64cf440331f35e8009f5",
"view_tag": "86"
}
}
}
],
"extra": [ 1, 84, 125, 50, 192, 41, 193, 133, 97, 249, 230, 159, 191, 92, 48, 113, 111, 245, 129, 176, 29, 47, 234, 156, 210, 17, 209, 21, 25, 101, 88, 240, 139, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}