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: cde8a8ae2e26f0b40e8c36018e6bb52ba02a45c6dc42ef21523dbe6da31dbb9c
Tx prefix hash: 8139373731be200c0f9fce0b20b0ad539af46e26f598ae300c82a5c2b30be5c2
Tx public key: 4a18efe9e4be60923b47b7e57bf4529cfae7ee3fb38386db0636df2299708368
| Timestamp: 1780051195 | Timestamp [UTC]: 2026-05-29 10:39:55 | Age [y:d:h:m:s]: 00:018:21:42:24 |
| Block: 4397 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4348 | RingCT/type: yes/0 |
| Extra: 014a18efe9e4be60923b47b7e57bf4529cfae7ee3fb38386db0636df229970836802090000000426697be300 | ||
1 output(s) for total of 34.890594582561 HMNY
| stealth address | amount | amount idx | tag |
| 00: 48808d8c592a216d22739ff15cc8ddc71596160a78414e9289d3fb1ad9221aee | 34.890594582561 | 5502 of 0 | <b3> |
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": 4457,
"vin": [ {
"gen": {
"height": 4397
}
}
],
"vout": [ {
"amount": 34890594582561,
"target": {
"tagged_key": {
"key": "48808d8c592a216d22739ff15cc8ddc71596160a78414e9289d3fb1ad9221aee",
"view_tag": "b3"
}
}
}
],
"extra": [ 1, 74, 24, 239, 233, 228, 190, 96, 146, 59, 71, 183, 229, 123, 244, 82, 156, 250, 231, 238, 63, 179, 131, 134, 219, 6, 54, 223, 34, 153, 112, 131, 104, 2, 9, 0, 0, 0, 4, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}