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: c6a8280696521ccfb78a8c16e2315a4ac047d8a0d3a0cd35e994c84c94c6f97d
Tx prefix hash: e6b46e6af608ad37b2d10eec4add2aad171fd832e5ba1362c2c07fd082911393
Tx public key: 87596cdf62198f0add162d70eb609f2adbb1242015e852e69dde6e875f4d9fe6
| Timestamp: 1779633373 | Timestamp [UTC]: 2026-05-24 14:36:13 | Age [y:d:h:m:s]: 00:015:10:10:34 |
| Block: 982 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6904 | RingCT/type: yes/0 |
| Extra: 0187596cdf62198f0add162d70eb609f2adbb1242015e852e69dde6e875f4d9fe6020900000001ba6d17be00 | ||
1 output(s) for total of 35.118599783402 HMNY
| stealth address | amount | amount idx | tag |
| 00: 6ec5dc322f00377fd55bb224c20c37823b11773172b1df2589a423b46dd2b27c | 35.118599783402 | 1118 of 0 | <bf> |
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": 1042,
"vin": [ {
"gen": {
"height": 982
}
}
],
"vout": [ {
"amount": 35118599783402,
"target": {
"tagged_key": {
"key": "6ec5dc322f00377fd55bb224c20c37823b11773172b1df2589a423b46dd2b27c",
"view_tag": "bf"
}
}
}
],
"extra": [ 1, 135, 89, 108, 223, 98, 25, 143, 10, 221, 22, 45, 112, 235, 96, 159, 42, 219, 177, 36, 32, 21, 232, 82, 230, 157, 222, 110, 135, 95, 77, 159, 230, 2, 9, 0, 0, 0, 1, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}