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: 2757159fe0aa535c88bf364ac5a1b297fb6ce8f27d8943ecfa1e2d9c7879c6f3
Tx prefix hash: df606b1f640683a667999acbbd85c21c25b0a3fd4a4f1f29b0a32e26c71950b9
Tx public key: 03a13177e9d835a769e2ca50a0df03d1da24992445e8b8a1aa9ed2cd83dc1270
| Timestamp: 1780104363 | Timestamp [UTC]: 2026-05-30 01:26:03 | Age [y:d:h:m:s]: 00:009:21:52:50 |
| Block: 4842 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3044 | RingCT/type: yes/0 |
| Extra: 0103a13177e9d835a769e2ca50a0df03d1da24992445e8b8a1aa9ed2cd83dc127002090000001a26697be300 | ||
1 output(s) for total of 34.863612623664 HMNY
| stealth address | amount | amount idx | tag |
| 00: ad2da2b7f0d41319686753ff8cd04477a150c9b51f32420558da9a69ab818862 | 34.863612623664 | 6104 of 0 | <23> |
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": 4902,
"vin": [ {
"gen": {
"height": 4842
}
}
],
"vout": [ {
"amount": 34863612623664,
"target": {
"tagged_key": {
"key": "ad2da2b7f0d41319686753ff8cd04477a150c9b51f32420558da9a69ab818862",
"view_tag": "23"
}
}
}
],
"extra": [ 1, 3, 161, 49, 119, 233, 216, 53, 167, 105, 226, 202, 80, 160, 223, 3, 209, 218, 36, 153, 36, 69, 232, 184, 161, 170, 158, 210, 205, 131, 220, 18, 112, 2, 9, 0, 0, 0, 26, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}