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: c86a4c2f4dbeeed7d73566face4579ede8605c3f4b8bef655e0a45a7f55a796b
Tx prefix hash: 12d56288e536966053f90acaab4cc0bfed6b0fcebbf4b2d251a26b793de4e922
Tx public key: 9e6c4f941ee9fcc4cabe16cbfdb27995e3ad2c0f4ab038773fffd1cdb316c6cc
| Timestamp: 1779852157 | Timestamp [UTC]: 2026-05-27 03:22:37 | Age [y:d:h:m:s]: 00:012:22:13:20 |
| Block: 2547 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5339 | RingCT/type: yes/0 |
| Extra: 019e6c4f941ee9fcc4cabe16cbfdb27995e3ad2c0f4ab038773fffd1cdb316c6cc02090000000226697be300 | ||
1 output(s) for total of 35.013926943756 HMNY
| stealth address | amount | amount idx | tag |
| 00: 75f14f40d8660f386b602eca8725d03b305079d5431603135dbdc35a6b45a56f | 35.013926943756 | 2999 of 0 | <eb> |
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": 2607,
"vin": [ {
"gen": {
"height": 2547
}
}
],
"vout": [ {
"amount": 35013926943756,
"target": {
"tagged_key": {
"key": "75f14f40d8660f386b602eca8725d03b305079d5431603135dbdc35a6b45a56f",
"view_tag": "eb"
}
}
}
],
"extra": [ 1, 158, 108, 79, 148, 30, 233, 252, 196, 202, 190, 22, 203, 253, 178, 121, 149, 227, 173, 44, 15, 74, 176, 56, 119, 63, 255, 209, 205, 179, 22, 198, 204, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}