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: eb4a9f45908aa343ba97b1f7fc433fb6d66e2d9634d6f680ecdfad9b3f682d5f
Tx prefix hash: d2d11740f6a2d7ff9aadc7a0c374bc2308a72b9b6b762b411d5a70edd353163c
Tx public key: aeefb15fd3077b6ec69993cdee16a72cea1c2e2feae106dcdc52d85d0b47fb45
| Timestamp: 1779468425 | Timestamp [UTC]: 2026-05-22 16:47:05 | Age [y:d:h:m:s]: 00:017:08:48:52 |
| Block: 539 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7347 | RingCT/type: yes/0 |
| Extra: 01aeefb15fd3077b6ec69993cdee16a72cea1c2e2feae106dcdc52d85d0b47fb4502090000000793369e7d00 | ||
1 output(s) for total of 35.148286003798 HMNY
| stealth address | amount | amount idx | tag |
| 00: daf0051f64740a2fc2fc9e1659caf99f16104a7544148559fb36d4ccf4a11b7d | 35.148286003798 | 543 of 0 | <9f> |
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": 599,
"vin": [ {
"gen": {
"height": 539
}
}
],
"vout": [ {
"amount": 35148286003798,
"target": {
"tagged_key": {
"key": "daf0051f64740a2fc2fc9e1659caf99f16104a7544148559fb36d4ccf4a11b7d",
"view_tag": "9f"
}
}
}
],
"extra": [ 1, 174, 239, 177, 95, 211, 7, 123, 110, 198, 153, 147, 205, 238, 22, 167, 44, 234, 28, 46, 47, 234, 225, 6, 220, 220, 82, 216, 93, 11, 71, 251, 69, 2, 9, 0, 0, 0, 7, 147, 54, 158, 125, 0
],
"rct_signatures": {
"type": 0
}
}