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: 21e92789bc3cc4d8e6da69900ce5764b10248bcafc46f8995e5882592a41161b
Tx prefix hash: 8f03ea915d6b69ecfc05d4ded591b8d8b2ae994b2845a3fd51d22b41cd972a7f
Tx public key: caeda979ea478288d16828c8259e717d314b74132d1c9d808a52c8b5dcf87b97
| Timestamp: 1780686046 | Timestamp [UTC]: 2026-06-05 19:00:46 | Age [y:d:h:m:s]: 00:003:06:35:11 |
| Block: 5410 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2476 | RingCT/type: yes/0 |
| Extra: 01caeda979ea478288d16828c8259e717d314b74132d1c9d808a52c8b5dcf87b97020900000001e49593ff00 | ||
1 output(s) for total of 34.823245944187 HMNY
| stealth address | amount | amount idx | tag |
| 00: 2cd5465353a4d1f7adf4921ad4b4a2ff5e17cb8f7e3c6371cb6b9d9bcd3ec692 | 34.823245944187 | 6847 of 0 | <b3> |
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": 5470,
"vin": [ {
"gen": {
"height": 5410
}
}
],
"vout": [ {
"amount": 34823245944187,
"target": {
"tagged_key": {
"key": "2cd5465353a4d1f7adf4921ad4b4a2ff5e17cb8f7e3c6371cb6b9d9bcd3ec692",
"view_tag": "b3"
}
}
}
],
"extra": [ 1, 202, 237, 169, 121, 234, 71, 130, 136, 209, 104, 40, 200, 37, 158, 113, 125, 49, 75, 116, 19, 45, 28, 157, 128, 138, 82, 200, 181, 220, 248, 123, 151, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}