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: 3daab4c3db776caaf3a0d5610e480429c7bc76ec16c83dded82cbaa85b50327b
Tx prefix hash: d6156b8a56742d4ce471835d2e8243693861dfd0a95be5544a6b8c47e89c70c3
Tx public key: 2047e0343e469fc477b3b96bab3c19636e2ab5c52b9f963c47f0a3a35321c5bd
| Timestamp: 1780056804 | Timestamp [UTC]: 2026-05-29 12:13:24 | Age [y:d:h:m:s]: 00:010:12:33:23 |
| Block: 4467 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3419 | RingCT/type: yes/0 |
| Extra: 012047e0343e469fc477b3b96bab3c19636e2ab5c52b9f963c47f0a3a35321c5bd02090000000826697be300 | ||
1 output(s) for total of 34.885936492136 HMNY
| stealth address | amount | amount idx | tag |
| 00: 90f1cabcdbc5747f423b454cfa0bf9351d7bac97909a81ee164c7162ecf8f220 | 34.885936492136 | 5593 of 0 | <ee> |
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": 4527,
"vin": [ {
"gen": {
"height": 4467
}
}
],
"vout": [ {
"amount": 34885936492136,
"target": {
"tagged_key": {
"key": "90f1cabcdbc5747f423b454cfa0bf9351d7bac97909a81ee164c7162ecf8f220",
"view_tag": "ee"
}
}
}
],
"extra": [ 1, 32, 71, 224, 52, 62, 70, 159, 196, 119, 179, 185, 107, 171, 60, 25, 99, 110, 42, 181, 197, 43, 159, 150, 60, 71, 240, 163, 163, 83, 33, 197, 189, 2, 9, 0, 0, 0, 8, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}