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: 48b9472c1e08da417c828860ee31cd2f57f9cc33e6c849e7335edc0a81291c74
Tx prefix hash: 0001288f25b3e8905aea954eee971b42954d1275d43ac1771612d16162393114
Tx public key: ff6d21d177630fe5df6cae34dafc113af15358dd94ca18ea5e4ac3e9c08fb4d2
| Timestamp: 1779790766 | Timestamp [UTC]: 2026-05-26 10:19:26 | Age [y:d:h:m:s]: 00:013:15:16:31 |
| Block: 2220 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5666 | RingCT/type: yes/0 |
| Extra: 01ff6d21d177630fe5df6cae34dafc113af15358dd94ca18ea5e4ac3e9c08fb4d202090000000126697be300 | ||
1 output(s) for total of 35.046360867695 HMNY
| stealth address | amount | amount idx | tag |
| 00: 42055800d301dad1ad567e3d6a4dfc29bc3c73eda0335d9d3a5ffa30e1fa78ec | 35.046360867695 | 2570 of 0 | <0e> |
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": 2280,
"vin": [ {
"gen": {
"height": 2220
}
}
],
"vout": [ {
"amount": 35046360867695,
"target": {
"tagged_key": {
"key": "42055800d301dad1ad567e3d6a4dfc29bc3c73eda0335d9d3a5ffa30e1fa78ec",
"view_tag": "0e"
}
}
}
],
"extra": [ 1, 255, 109, 33, 209, 119, 99, 15, 229, 223, 108, 174, 52, 218, 252, 17, 58, 241, 83, 88, 221, 148, 202, 24, 234, 94, 74, 195, 233, 192, 143, 180, 210, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}