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: e0c325faa0326305a65598e83a93dee1176cf5f7ffdc4d06e266642d49ab6148
Tx prefix hash: d8c51ea7e28290d0c7d4c2ad79e30eb2463f3f77eb8c063af9f048655cbe382c
Tx public key: a0e67bd7d5f81f9f341e0ea06162225edb72352e8555a4caf8836c2fcb946d97
| Timestamp: 1780755121 | Timestamp [UTC]: 2026-06-06 14:12:01 | Age [y:d:h:m:s]: 00:002:13:26:49 |
| Block: 6523 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1419 | RingCT/type: yes/0 |
| Extra: 01a0e67bd7d5f81f9f341e0ea06162225edb72352e8555a4caf8836c2fcb946d97020900000001e49593ff00 | ||
1 output(s) for total of 34.753620347314 HMNY
| stealth address | amount | amount idx | tag |
| 00: ba6bec4dd2f5689e9a949eccdb4d12566fa3dc5f8285428df3e5a12e85509dc4 | 34.753620347314 | 8023 of 0 | <1b> |
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": 6583,
"vin": [ {
"gen": {
"height": 6523
}
}
],
"vout": [ {
"amount": 34753620347314,
"target": {
"tagged_key": {
"key": "ba6bec4dd2f5689e9a949eccdb4d12566fa3dc5f8285428df3e5a12e85509dc4",
"view_tag": "1b"
}
}
}
],
"extra": [ 1, 160, 230, 123, 215, 213, 248, 31, 159, 52, 30, 14, 160, 97, 98, 34, 94, 219, 114, 53, 46, 133, 85, 164, 202, 248, 131, 108, 47, 203, 148, 109, 151, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}