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: d2c92aa25d6cf865ef5cd0b298fe483e3e8f5d2d765c31c0f66d82291fc0496d
Tx prefix hash: 1785ba15d9b11897ebd16a7ab4f344777cd4401b85b427219b96eb33a9e04b03
Tx public key: 31986a7fa92c3613c6b08256c97c5df6b5c5889b8e0a604134a367069dc967ac
| Timestamp: 1779895323 | Timestamp [UTC]: 2026-05-27 15:22:03 | Age [y:d:h:m:s]: 00:012:11:18:33 |
| Block: 3101 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4795 | RingCT/type: yes/0 |
| Extra: 0131986a7fa92c3613c6b08256c97c5df6b5c5889b8e0a604134a367069dc967ac02090000000426697be300 | ||
1 output(s) for total of 34.976948242905 HMNY
| stealth address | amount | amount idx | tag |
| 00: c477a6f416eb731fbc3513706de99737c7ec2d19d82fe30623790e508f298432 | 34.976948242905 | 3697 of 0 | <70> |
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": 3161,
"vin": [ {
"gen": {
"height": 3101
}
}
],
"vout": [ {
"amount": 34976948242905,
"target": {
"tagged_key": {
"key": "c477a6f416eb731fbc3513706de99737c7ec2d19d82fe30623790e508f298432",
"view_tag": "70"
}
}
}
],
"extra": [ 1, 49, 152, 106, 127, 169, 44, 54, 19, 198, 176, 130, 86, 201, 124, 93, 246, 181, 197, 136, 155, 142, 10, 96, 65, 52, 163, 103, 6, 157, 201, 103, 172, 2, 9, 0, 0, 0, 4, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}