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: 3def30d180eb130418ae4e4bb7228be19635dc5d56efa2cad4fced92cfe881fa
Tx prefix hash: c38d5d979789d5b628f7a3ba87ab106d39a515546e30b8df0034ac37c3bd009d
Tx public key: c7e1ec52556466dbe8e02fffb38c9865e2e38df0d868e3b633c64eef31fe60f0
| Timestamp: 1780110800 | Timestamp [UTC]: 2026-05-30 03:13:20 | Age [y:d:h:m:s]: 00:010:13:55:43 |
| Block: 4854 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3880 | RingCT/type: yes/0 |
| Extra: 01c7e1ec52556466dbe8e02fffb38c9865e2e38df0d868e3b633c64eef31fe60f002090000000126697be300 | ||
1 output(s) for total of 34.860195127225 HMNY
| stealth address | amount | amount idx | tag |
| 00: caf555c95453aa8fadd7250a3c56abe485410b3925fb821f0efc56f2c5884a76 | 34.860195127225 | 6128 of 0 | <bc> |
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": 4914,
"vin": [ {
"gen": {
"height": 4854
}
}
],
"vout": [ {
"amount": 34860195127225,
"target": {
"tagged_key": {
"key": "caf555c95453aa8fadd7250a3c56abe485410b3925fb821f0efc56f2c5884a76",
"view_tag": "bc"
}
}
}
],
"extra": [ 1, 199, 225, 236, 82, 85, 100, 102, 219, 232, 224, 47, 255, 179, 140, 152, 101, 226, 227, 141, 240, 216, 104, 227, 182, 51, 198, 78, 239, 49, 254, 96, 240, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}