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: 3b28132259875692b3a9647089bdee3dd9462b90a933db85d2e3393977da1150
Tx prefix hash: 88e7eb6be10f2936fe4ca3c285e00bb83851e21238ab2c3043ab685cd6eaecfd
Tx public key: 07618f904650b168b2ded132b7a97c5fbf7411b5d46e7a5c4f68e2ccea6bec67
| Timestamp: 1779987036 | Timestamp [UTC]: 2026-05-28 16:50:36 | Age [y:d:h:m:s]: 00:011:08:45:21 |
| Block: 3965 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3921 | RingCT/type: yes/0 |
| Extra: 0107618f904650b168b2ded132b7a97c5fbf7411b5d46e7a5c4f68e2ccea6bec6702090000000326697be300 | ||
1 output(s) for total of 34.919355421505 HMNY
| stealth address | amount | amount idx | tag |
| 00: d2c17b3007f94808a15dcc276ab4e274b09cfbb426d83d23402789311d77928c | 34.919355421505 | 4890 of 0 | <7e> |
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": 4025,
"vin": [ {
"gen": {
"height": 3965
}
}
],
"vout": [ {
"amount": 34919355421505,
"target": {
"tagged_key": {
"key": "d2c17b3007f94808a15dcc276ab4e274b09cfbb426d83d23402789311d77928c",
"view_tag": "7e"
}
}
}
],
"extra": [ 1, 7, 97, 143, 144, 70, 80, 177, 104, 178, 222, 209, 50, 183, 169, 124, 95, 191, 116, 17, 181, 212, 110, 122, 92, 79, 104, 226, 204, 234, 107, 236, 103, 2, 9, 0, 0, 0, 3, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}