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: 13092b8eee6880afb52f26393ddaa2bc0176cd21c23f0d85cfe668002c1c3792
Tx prefix hash: 5eba6d8d8d0688557c82dd79a779068d511bfe194482a2f46d58c59e0f850718
Tx public key: 0e0f9fe1d7f63c2b3297f0965f77985cd5b724cd0dd4a8ced9c247f1f312eb6a
| Timestamp: 1780687263 | Timestamp [UTC]: 2026-06-05 19:21:03 | Age [y:d:h:m:s]: 00:003:06:14:54 |
| Block: 5471 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2415 | RingCT/type: yes/0 |
| Extra: 010e0f9fe1d7f63c2b3297f0965f77985cd5b724cd0dd4a8ced9c247f1f312eb6a020900000001e49593ff00 | ||
1 output(s) for total of 34.819194551711 HMNY
| stealth address | amount | amount idx | tag |
| 00: bf415af16f9cfe09ec149a84931e2b899e040b3c16e646d050116c3667ff1bc9 | 34.819194551711 | 6910 of 0 | <a0> |
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": 5531,
"vin": [ {
"gen": {
"height": 5471
}
}
],
"vout": [ {
"amount": 34819194551711,
"target": {
"tagged_key": {
"key": "bf415af16f9cfe09ec149a84931e2b899e040b3c16e646d050116c3667ff1bc9",
"view_tag": "a0"
}
}
}
],
"extra": [ 1, 14, 15, 159, 225, 215, 246, 60, 43, 50, 151, 240, 150, 95, 119, 152, 92, 213, 183, 36, 205, 13, 212, 168, 206, 217, 194, 71, 241, 243, 18, 235, 106, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}