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: 5fb0fc21dcb18fec6a4dbbc06b3b6c26a191113edbf43861a239da067c148cf1
Tx prefix hash: c1e2f2e275f3bc025fa023476d06c9aab5056efa1bfb7daa99cdb0e6cc93bdd6
Tx public key: 7eaeeeb1352fb727a4101ef3fbc8db33b08c1d439d4a6fe76757a074a2f03a6c
| Timestamp: 1780762644 | Timestamp [UTC]: 2026-06-06 16:17:24 | Age [y:d:h:m:s]: 00:010:15:47:57 |
| Block: 6587 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2158 | RingCT/type: yes/0 |
| Extra: 017eaeeeb1352fb727a4101ef3fbc8db33b08c1d439d4a6fe76757a074a2f03a6c020900000002e49593ff00 | ||
1 output(s) for total of 34.745157132197 HMNY
| stealth address | amount | amount idx | tag |
| 00: f25969acd83933ce1862836d8f136d1fc6cc370d2f60dacc26d98a3e6554dded | 34.745157132197 | 8113 of 0 | <44> |
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": 6647,
"vin": [ {
"gen": {
"height": 6587
}
}
],
"vout": [ {
"amount": 34745157132197,
"target": {
"tagged_key": {
"key": "f25969acd83933ce1862836d8f136d1fc6cc370d2f60dacc26d98a3e6554dded",
"view_tag": "44"
}
}
}
],
"extra": [ 1, 126, 174, 238, 177, 53, 47, 183, 39, 164, 16, 30, 243, 251, 200, 219, 51, 176, 140, 29, 67, 157, 74, 111, 231, 103, 87, 160, 116, 162, 240, 58, 108, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}