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: 5d8b55148d49fa6dcf0e1513fc283b6431a67a164f0649d1c2a509e7fc49edbd
Tx prefix hash: 05949e052c08a4fa0d6b196279b7216fd1aa95538a3dac80f076431916a0977e
Tx public key: 6bb16a821a4cf8d73a2fe6e99044fbcff309bfa5c176781deae8ddab1be51dd9
| Timestamp: 1780832215 | Timestamp [UTC]: 2026-06-07 11:36:55 | Age [y:d:h:m:s]: 00:001:13:09:52 |
| Block: 7359 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 527 | RingCT/type: yes/0 |
| Extra: 016bb16a821a4cf8d73a2fe6e99044fbcff309bfa5c176781deae8ddab1be51dd9020900000003e49593ff00 | ||
1 output(s) for total of 34.694033421045 HMNY
| stealth address | amount | amount idx | tag |
| 00: 9e4c62d76e3077f23a8341b03af05af23415c681b28f3ff6cfd14b029490c02f | 34.694033421045 | 9059 of 0 | <8a> |
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": 7419,
"vin": [ {
"gen": {
"height": 7359
}
}
],
"vout": [ {
"amount": 34694033421045,
"target": {
"tagged_key": {
"key": "9e4c62d76e3077f23a8341b03af05af23415c681b28f3ff6cfd14b029490c02f",
"view_tag": "8a"
}
}
}
],
"extra": [ 1, 107, 177, 106, 130, 26, 76, 248, 215, 58, 47, 230, 233, 144, 68, 251, 207, 243, 9, 191, 165, 193, 118, 120, 29, 234, 232, 221, 171, 27, 229, 29, 217, 2, 9, 0, 0, 0, 3, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}