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: 54d667f0f3a16e256bf6b1fcd40f54b8d9796b0f834616d32c18b9d398c1eb11
Tx prefix hash: d8b3527a928819811e1140988d9b038efc417275dbc581c481259007704f7038
Tx public key: 372a4feecbade5de12efe266dc4b4b0fee9afb3ca4cd6e27f1a8ba9dcd8d28f1
| Timestamp: 1780858842 | Timestamp [UTC]: 2026-06-07 19:00:42 | Age [y:d:h:m:s]: 00:001:06:35:15 |
| Block: 7596 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 290 | RingCT/type: yes/0 |
| Extra: 01372a4feecbade5de12efe266dc4b4b0fee9afb3ca4cd6e27f1a8ba9dcd8d28f1020900000001e49593ff00 | ||
1 output(s) for total of 34.681776203000 HMNY
| stealth address | amount | amount idx | tag |
| 00: 331ac947588ea437cfc9c371c6acbb1fdb8dedeab3f6fc54e71e3d7bd972ce4c | 34.681776203000 | 9384 of 0 | <ea> |
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": 7656,
"vin": [ {
"gen": {
"height": 7596
}
}
],
"vout": [ {
"amount": 34681776203000,
"target": {
"tagged_key": {
"key": "331ac947588ea437cfc9c371c6acbb1fdb8dedeab3f6fc54e71e3d7bd972ce4c",
"view_tag": "ea"
}
}
}
],
"extra": [ 1, 55, 42, 79, 238, 203, 173, 229, 222, 18, 239, 226, 102, 220, 75, 75, 15, 238, 154, 251, 60, 164, 205, 110, 39, 241, 168, 186, 157, 205, 141, 40, 241, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}