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: 536e8553e8bc5bba9eca2e666cffa0c89aa1b3866ff6dad6e24219b632988c8b
Tx prefix hash: 06b3239217f640662f9e8e25a2dc6accd2639505a38581d4312855355d404a29
Tx public key: aca09901c2a17d70f61b14d11a7ea4ddd86e645a969189abd5fa88a662419fd7
| Timestamp: 1780861757 | Timestamp [UTC]: 2026-06-07 19:49:17 | Age [y:d:h:m:s]: 00:001:01:22:50 |
| Block: 7627 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 259 | RingCT/type: yes/0 |
| Extra: 01aca09901c2a17d70f61b14d11a7ea4ddd86e645a969189abd5fa88a662419fd7020900000002e49593ff00 | ||
1 output(s) for total of 34.676303406630 HMNY
| stealth address | amount | amount idx | tag |
| 00: 7156268d5629b2ea860b846145ef87c7b8d0b071f54c66fc5e8203e427a56902 | 34.676303406630 | 9425 of 0 | <e0> |
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": 7687,
"vin": [ {
"gen": {
"height": 7627
}
}
],
"vout": [ {
"amount": 34676303406630,
"target": {
"tagged_key": {
"key": "7156268d5629b2ea860b846145ef87c7b8d0b071f54c66fc5e8203e427a56902",
"view_tag": "e0"
}
}
}
],
"extra": [ 1, 172, 160, 153, 1, 194, 161, 125, 112, 246, 27, 20, 209, 26, 126, 164, 221, 216, 110, 100, 90, 150, 145, 137, 171, 213, 250, 136, 166, 98, 65, 159, 215, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}