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: 60c42267ccd26f6696974a4a2fd3264c17a086dd486f8fe84bc108f018daa821
Tx prefix hash: 2e22c4d8050517b56f2dcfb20b90d0f5344b2e3192a92c0a603a5de61eb77725
Tx public key: b19a3439cb8821831a29e1e8fac1b49145e0c77467cd514281f312dade3429dc
| Timestamp: 1780983291 | Timestamp [UTC]: 2026-06-09 05:34:51 | Age [y:d:h:m:s]: 00:000:04:35:12 |
| Block: 8087 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 334 | RingCT/type: yes/0 |
| Extra: 01b19a3439cb8821831a29e1e8fac1b49145e0c77467cd514281f312dade3429dc020900000002e49593ff00 | ||
1 output(s) for total of 34.645892412633 HMNY
| stealth address | amount | amount idx | tag |
| 00: 045a1992c1a69b75ff0ef746247fd02f161c27e1bb94e66d853007f13d32ab8e | 34.645892412633 | 10019 of 0 | <91> |
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": 8147,
"vin": [ {
"gen": {
"height": 8087
}
}
],
"vout": [ {
"amount": 34645892412633,
"target": {
"tagged_key": {
"key": "045a1992c1a69b75ff0ef746247fd02f161c27e1bb94e66d853007f13d32ab8e",
"view_tag": "91"
}
}
}
],
"extra": [ 1, 177, 154, 52, 57, 203, 136, 33, 131, 26, 41, 225, 232, 250, 193, 180, 145, 69, 224, 199, 116, 103, 205, 81, 66, 129, 243, 18, 218, 222, 52, 41, 220, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}