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: 83fcf8865ddc70815055f043b87adc7096348f74d6a55f22015cc09a4377d06f
Tx prefix hash: a8d6dc571555906635a578d840f34e2f0c1cc2f007bf92e7362845e3ac95fb3a
Tx public key: 643f59b3c93d1e1833001ede70287456593717e9fef16b6284680ee7f937c033
| Timestamp: 1780759484 | Timestamp [UTC]: 2026-06-06 15:24:44 | Age [y:d:h:m:s]: 00:002:13:08:18 |
| Block: 6558 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1472 | RingCT/type: yes/0 |
| Extra: 01643f59b3c93d1e1833001ede70287456593717e9fef16b6284680ee7f937c033020900000001e49593ff00 | ||
1 output(s) for total of 34.747079049894 HMNY
| stealth address | amount | amount idx | tag |
| 00: a0a32df82648d9d073e60f564b7d9a080ac0e504edff687777444d810cde3a7c | 34.747079049894 | 8074 of 0 | <87> |
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": 6618,
"vin": [ {
"gen": {
"height": 6558
}
}
],
"vout": [ {
"amount": 34747079049894,
"target": {
"tagged_key": {
"key": "a0a32df82648d9d073e60f564b7d9a080ac0e504edff687777444d810cde3a7c",
"view_tag": "87"
}
}
}
],
"extra": [ 1, 100, 63, 89, 179, 201, 61, 30, 24, 51, 0, 30, 222, 112, 40, 116, 86, 89, 55, 23, 233, 254, 241, 107, 98, 132, 104, 14, 231, 249, 55, 192, 51, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}