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: 8d20a4858d7abdbdac809e36926d879f04e4b689c87aafb3f59ac266fbbe3e62
Tx prefix hash: bc85fc895accb84d5a05b4165e3b233de4c3048ff47c0649926cb82d0703cbfa
Tx public key: d0768702dfff524c9b8e15eb5530c4c49bdfb7eb4b9270b6353c2ae923b4d89e
| Timestamp: 1780801307 | Timestamp [UTC]: 2026-06-07 03:01:47 | Age [y:d:h:m:s]: 00:008:05:17:48 |
| Block: 6842 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1903 | RingCT/type: yes/0 |
| Extra: 01d0768702dfff524c9b8e15eb5530c4c49bdfb7eb4b9270b6353c2ae923b4d89e020900000001e49593ff00 | ||
1 output(s) for total of 34.728262087444 HMNY
| stealth address | amount | amount idx | tag |
| 00: 69d1e3866c446223326b821b05796248a83195bed40354dd687236cd93e94860 | 34.728262087444 | 8448 of 0 | <f0> |
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": 6902,
"vin": [ {
"gen": {
"height": 6842
}
}
],
"vout": [ {
"amount": 34728262087444,
"target": {
"tagged_key": {
"key": "69d1e3866c446223326b821b05796248a83195bed40354dd687236cd93e94860",
"view_tag": "f0"
}
}
}
],
"extra": [ 1, 208, 118, 135, 2, 223, 255, 82, 76, 155, 142, 21, 235, 85, 48, 196, 196, 155, 223, 183, 235, 75, 146, 112, 182, 53, 60, 42, 233, 35, 180, 216, 158, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}