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: 02097ca9d88b14215608a33143f795a4a2e3ce4ad60d36daa745de6efb6b66c7
Tx prefix hash: 406c6ff5fffd1de2cade65c06eba1d980efb6524b76a86047c4b0653a72eaea7
Tx public key: 63ea530a427adf912a02d803f826b30714ed22146a5972d4cb2f3663da9cfa98
| Timestamp: 1780748230 | Timestamp [UTC]: 2026-06-06 12:17:10 | Age [y:d:h:m:s]: 00:002:11:01:43 |
| Block: 6465 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1421 | RingCT/type: yes/0 |
| Extra: 0163ea530a427adf912a02d803f826b30714ed22146a5972d4cb2f3663da9cfa98020900000002e49593ff00 | ||
1 output(s) for total of 34.753243158278 HMNY
| stealth address | amount | amount idx | tag |
| 00: 92a9f45c5ecfa25c2cdcd01694d40f387a5b45de1864c181c284fed65fcb85e7 | 34.753243158278 | 7960 of 0 | <5d> |
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": 6525,
"vin": [ {
"gen": {
"height": 6465
}
}
],
"vout": [ {
"amount": 34753243158278,
"target": {
"tagged_key": {
"key": "92a9f45c5ecfa25c2cdcd01694d40f387a5b45de1864c181c284fed65fcb85e7",
"view_tag": "5d"
}
}
}
],
"extra": [ 1, 99, 234, 83, 10, 66, 122, 223, 145, 42, 2, 216, 3, 248, 38, 179, 7, 20, 237, 34, 20, 106, 89, 114, 212, 203, 47, 54, 99, 218, 156, 250, 152, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}