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: 836aaa63a0a4ea39e5f931af957cfd705d5ac51825af3bee1cfc578bd6c5eda5
Tx prefix hash: 5648e3e64d7659a2dc2b64246c02ae664723aaaf06c3251d17b822fa5eee21db
Tx public key: 2b8c96eb50a9cb25adbe33c7b2358e392d21a9e97ebe05e883f7d1c4420122fb
| Timestamp: 1780981552 | Timestamp [UTC]: 2026-06-09 05:05:52 | Age [y:d:h:m:s]: 00:000:07:31:53 |
| Block: 8042 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 530 | RingCT/type: yes/0 |
| Extra: 012b8c96eb50a9cb25adbe33c7b2358e392d21a9e97ebe05e883f7d1c4420122fb020900000001e49593ff00 | ||
1 output(s) for total of 34.648866223888 HMNY
| stealth address | amount | amount idx | tag |
| 00: 74e45da9e435082a9cd9013acb7284a4e3f4790798757e35ad4d77544be45d9c | 34.648866223888 | 9968 of 0 | <a5> |
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": 8102,
"vin": [ {
"gen": {
"height": 8042
}
}
],
"vout": [ {
"amount": 34648866223888,
"target": {
"tagged_key": {
"key": "74e45da9e435082a9cd9013acb7284a4e3f4790798757e35ad4d77544be45d9c",
"view_tag": "a5"
}
}
}
],
"extra": [ 1, 43, 140, 150, 235, 80, 169, 203, 37, 173, 190, 51, 199, 178, 53, 142, 57, 45, 33, 169, 233, 126, 190, 5, 232, 131, 247, 209, 196, 66, 1, 34, 251, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}