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: 2bbf314008b188a990d3e32ac133ab1d5239da8de64c3b280a3c2f88513612bd
Tx prefix hash: d26d92c118eed148bd3d0d22da6cc012c50d26b760179c047695ca85f77c4e5b
Tx public key: bd0ab2ab30eaab2e632960126beab0c64b50e9f1c42fcb6a14314f0a03cf487d
| Timestamp: 1780817983 | Timestamp [UTC]: 2026-06-07 07:39:43 | Age [y:d:h:m:s]: 00:001:17:56:14 |
| Block: 7099 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 787 | RingCT/type: yes/0 |
| Extra: 01bd0ab2ab30eaab2e632960126beab0c64b50e9f1c42fcb6a14314f0a03cf487d020900000001e49593ff00 | ||
1 output(s) for total of 34.717860844748 HMNY
| stealth address | amount | amount idx | tag |
| 00: 954f93fb0f235cac4f1960f560f57158de28e41a0de6d1b025858c8a8bb67882 | 34.717860844748 | 8751 of 0 | <33> |
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": 7159,
"vin": [ {
"gen": {
"height": 7099
}
}
],
"vout": [ {
"amount": 34717860844748,
"target": {
"tagged_key": {
"key": "954f93fb0f235cac4f1960f560f57158de28e41a0de6d1b025858c8a8bb67882",
"view_tag": "33"
}
}
}
],
"extra": [ 1, 189, 10, 178, 171, 48, 234, 171, 46, 99, 41, 96, 18, 107, 234, 176, 198, 75, 80, 233, 241, 196, 47, 203, 106, 20, 49, 79, 10, 3, 207, 72, 125, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}