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: 234ecad04f4b24f5fdf334bdd241ff751aef9f0ceb25fb2aee3345a6a7a82eae
Tx prefix hash: 3662e2cb10820ebb9aa1fd74bebd8116cb7f0935b9089bb2fe8d6aebc376c3e0
Tx public key: 029367f0a602e5b5ce884b2f399d9a8c49d45e0674632c135b658f36d6aac21e
| Timestamp: 1780694203 | Timestamp [UTC]: 2026-06-05 21:16:43 | Age [y:d:h:m:s]: 00:003:19:52:20 |
| Block: 5923 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2811 | RingCT/type: yes/0 |
| Extra: 01029367f0a602e5b5ce884b2f399d9a8c49d45e0674632c135b658f36d6aac21e020900000002e49593ff00 | ||
1 output(s) for total of 34.789189080044 HMNY
| stealth address | amount | amount idx | tag |
| 00: 01ddaae87f11625e574f1f860d0fdad3ded307bb734aa5c642efee0c2d2be799 | 34.789189080044 | 7384 of 0 | <e5> |
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": 5983,
"vin": [ {
"gen": {
"height": 5923
}
}
],
"vout": [ {
"amount": 34789189080044,
"target": {
"tagged_key": {
"key": "01ddaae87f11625e574f1f860d0fdad3ded307bb734aa5c642efee0c2d2be799",
"view_tag": "e5"
}
}
}
],
"extra": [ 1, 2, 147, 103, 240, 166, 2, 229, 181, 206, 136, 75, 47, 57, 157, 154, 140, 73, 212, 94, 6, 116, 99, 44, 19, 91, 101, 143, 54, 214, 170, 194, 30, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}