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: 170c21cb5afe3cfe3ca6cf2b945e0f5d94f72024f7a674b54b5edeb99ebb0a9e
Tx prefix hash: 1fa59ea8d3c04ed79eb1ddcd232033b5185ca1c1e7704ba09d43cc7c072450fb
Tx public key: de9fb4d891e04467ae66d39eea06c6f72e5e0e8dd1c93397edc2a30233ef0ddc
| Timestamp: 1779636382 | Timestamp [UTC]: 2026-05-24 15:26:22 | Age [y:d:h:m:s]: 00:015:11:14:14 |
| Block: 1111 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0820 kB |
| Tx version: 2 | No of confirmations: 6785 | RingCT/type: yes/0 |
| Extra: 01de9fb4d891e04467ae66d39eea06c6f72e5e0e8dd1c93397edc2a30233ef0ddc | ||
1 output(s) for total of 35.109959977796 HMNY
| stealth address | amount | amount idx | tag |
| 00: 6af4e7cff45ab44ae95e9918387e83bc27a3d58f51b72c8c35b28b9c3213bfe1 | 35.109959977796 | 1251 of 0 | <38> |
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": 1171,
"vin": [ {
"gen": {
"height": 1111
}
}
],
"vout": [ {
"amount": 35109959977796,
"target": {
"tagged_key": {
"key": "6af4e7cff45ab44ae95e9918387e83bc27a3d58f51b72c8c35b28b9c3213bfe1",
"view_tag": "38"
}
}
}
],
"extra": [ 1, 222, 159, 180, 216, 145, 224, 68, 103, 174, 102, 211, 158, 234, 6, 198, 247, 46, 94, 14, 141, 209, 201, 51, 151, 237, 194, 163, 2, 51, 239, 13, 220
],
"rct_signatures": {
"type": 0
}
}