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: 4e8ff5b895f43cd6a626e3c0852d47c1e7c7f28d56cdce65ee7a20d39daee3e7
Tx prefix hash: 6c4e49d5c41b5c981d96cc5d152737ab16a9376d2d14d535e6751524a92bce5d
Tx public key: 3a682c48a572fe295dcbbd0edba526ab18dd4d8eddb34cae3662ff0cd516ace8
| Timestamp: 1780764531 | Timestamp [UTC]: 2026-06-06 16:48:51 | Age [y:d:h:m:s]: 00:010:15:12:54 |
| Block: 6605 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2140 | RingCT/type: yes/0 |
| Extra: 013a682c48a572fe295dcbbd0edba526ab18dd4d8eddb34cae3662ff0cd516ace8020900000003e49593ff00 | ||
1 output(s) for total of 34.743964271234 HMNY
| stealth address | amount | amount idx | tag |
| 00: d2cf26d9555f402178bd0e7384bf0f2a58a51010c56d0b5a8e85bc0fdd2d0cd0 | 34.743964271234 | 8137 of 0 | <58> |
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": 6665,
"vin": [ {
"gen": {
"height": 6605
}
}
],
"vout": [ {
"amount": 34743964271234,
"target": {
"tagged_key": {
"key": "d2cf26d9555f402178bd0e7384bf0f2a58a51010c56d0b5a8e85bc0fdd2d0cd0",
"view_tag": "58"
}
}
}
],
"extra": [ 1, 58, 104, 44, 72, 165, 114, 254, 41, 93, 203, 189, 14, 219, 165, 38, 171, 24, 221, 77, 142, 221, 179, 76, 174, 54, 98, 255, 12, 213, 22, 172, 232, 2, 9, 0, 0, 0, 3, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}