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: 4266dab1692b8add1be6b0a9682ac2a87c35913ae03c7b9dc60608e20a7ddb7d
Tx prefix hash: 56d7b4c58ff264c48f09cab4fd52f1c23b1fd7a34b9da71b89bb5eba3b031209
Tx public key: db6ea7157092376341c9524730ce6aba9eb03f4d96a9b2a33f071677e65570ac
| Timestamp: 1780689734 | Timestamp [UTC]: 2026-06-05 20:02:14 | Age [y:d:h:m:s]: 00:003:07:36:36 |
| Block: 5616 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2331 | RingCT/type: yes/0 |
| Extra: 01db6ea7157092376341c9524730ce6aba9eb03f4d96a9b2a33f071677e65570ac020900000001e49593ff00 | ||
1 output(s) for total of 34.809566084288 HMNY
| stealth address | amount | amount idx | tag |
| 00: 4c44c5d3a25e300fee6b6a6fbbb1b6b9cb8f7a190fbb58547a67d6dd5d576463 | 34.809566084288 | 7063 of 0 | <01> |
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": 5676,
"vin": [ {
"gen": {
"height": 5616
}
}
],
"vout": [ {
"amount": 34809566084288,
"target": {
"tagged_key": {
"key": "4c44c5d3a25e300fee6b6a6fbbb1b6b9cb8f7a190fbb58547a67d6dd5d576463",
"view_tag": "01"
}
}
}
],
"extra": [ 1, 219, 110, 167, 21, 112, 146, 55, 99, 65, 201, 82, 71, 48, 206, 106, 186, 158, 176, 63, 77, 150, 169, 178, 163, 63, 7, 22, 119, 230, 85, 112, 172, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}