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: 68f39021c95daa18caaf81840ee678f7f2aef33d02bff06a005f40a605ee55e9
Tx prefix hash: 5cbbf4b46ea0ed5e65005ba6e5f291146114d3677b158101bbf077a3e272e920
Tx public key: 6c26aa4b84868264985db6ccc1d4ad3efad1b98d82519ccd35c58c2948bdc280
| Timestamp: 1779461946 | Timestamp [UTC]: 2026-05-22 14:59:06 | Age [y:d:h:m:s]: 00:017:09:47:41 |
| Block: 455 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7431 | RingCT/type: yes/0 |
| Extra: 016c26aa4b84868264985db6ccc1d4ad3efad1b98d82519ccd35c58c2948bdc28002090000000193369e7d00 | ||
1 output(s) for total of 35.153917823275 HMNY
| stealth address | amount | amount idx | tag |
| 00: 83d24091c7b07f68aad91717106efeb4725b071641bc6d5e528162725142a6f8 | 35.153917823275 | 459 of 0 | <4a> |
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": 515,
"vin": [ {
"gen": {
"height": 455
}
}
],
"vout": [ {
"amount": 35153917823275,
"target": {
"tagged_key": {
"key": "83d24091c7b07f68aad91717106efeb4725b071641bc6d5e528162725142a6f8",
"view_tag": "4a"
}
}
}
],
"extra": [ 1, 108, 38, 170, 75, 132, 134, 130, 100, 152, 93, 182, 204, 193, 212, 173, 62, 250, 209, 185, 141, 130, 81, 156, 205, 53, 197, 140, 41, 72, 189, 194, 128, 2, 9, 0, 0, 0, 1, 147, 54, 158, 125, 0
],
"rct_signatures": {
"type": 0
}
}