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: 4b3629b68b5e8eda85fffd5bade379e146957eb3aa8a92ed9ccf9a65673bd0f9
Tx prefix hash: 86b4c594f7683922e598f6d2525a3ed64d36c119923807bdabe7c144a530784b
Tx public key: 0557cb50c5a2337bdb3c9d37c9e9c1a1d1de21674363608c6d383ce0dc9aa89a
| Timestamp: 1779873675 | Timestamp [UTC]: 2026-05-27 09:21:15 | Age [y:d:h:m:s]: 00:020:22:44:06 |
| Block: 2846 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5899 | RingCT/type: yes/0 |
| Extra: 010557cb50c5a2337bdb3c9d37c9e9c1a1d1de21674363608c6d383ce0dc9aa89a02090000000226697be300 | ||
1 output(s) for total of 34.993964271648 HMNY
| stealth address | amount | amount idx | tag |
| 00: e726d9def79ec8b97de7e2fe25b33b3e3d5c283b194b5ca0f66e5902b0a0cc19 | 34.993964271648 | 3370 of 0 | <4e> |
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": 2906,
"vin": [ {
"gen": {
"height": 2846
}
}
],
"vout": [ {
"amount": 34993964271648,
"target": {
"tagged_key": {
"key": "e726d9def79ec8b97de7e2fe25b33b3e3d5c283b194b5ca0f66e5902b0a0cc19",
"view_tag": "4e"
}
}
}
],
"extra": [ 1, 5, 87, 203, 80, 197, 162, 51, 123, 219, 60, 157, 55, 201, 233, 193, 161, 209, 222, 33, 103, 67, 99, 96, 140, 109, 56, 60, 224, 220, 154, 168, 154, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}