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: 7ab3771f2f355ad9cb9e631ccde2489bca1626e7114c9853549f2781ec86a5a4
Tx prefix hash: 0f18aaf77cf1268d9cb9bac1ee9bd6a816ab6663f920d6013835c57bcfb73b78
Tx public key: 190cc00f581e3dc33f19aca51fb256b2c44e3fbe3c2928d31e9d39bc01bd5d5a
| Timestamp: 1779852293 | Timestamp [UTC]: 2026-05-27 03:24:53 | Age [y:d:h:m:s]: 00:012:23:24:55 |
| Block: 2549 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5371 | RingCT/type: yes/0 |
| Extra: 01190cc00f581e3dc33f19aca51fb256b2c44e3fbe3c2928d31e9d39bc01bd5d5a02090000000126697be300 | ||
1 output(s) for total of 35.013793376353 HMNY
| stealth address | amount | amount idx | tag |
| 00: b54ffc5b8eeafa8bfdb0daae920c78074a059faf6d6737c4925175821702c78d | 35.013793376353 | 3001 of 0 | <b4> |
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": 2609,
"vin": [ {
"gen": {
"height": 2549
}
}
],
"vout": [ {
"amount": 35013793376353,
"target": {
"tagged_key": {
"key": "b54ffc5b8eeafa8bfdb0daae920c78074a059faf6d6737c4925175821702c78d",
"view_tag": "b4"
}
}
}
],
"extra": [ 1, 25, 12, 192, 15, 88, 30, 61, 195, 63, 25, 172, 165, 31, 178, 86, 178, 196, 78, 63, 190, 60, 41, 40, 211, 30, 157, 57, 188, 1, 189, 93, 90, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}