Block Explorer
What is Explorer?
To uphold our commitment to security and transparency, we created Block Explorer, a tool that enables you to independently validate your transactions on the blockchain. Every transaction on our platform—whether it's a deposit, withdrawal, trading fee, realized profit/loss, funding event, or position opening/closing—is cryptographically rolled and posted on-chain from the central system which keeps the users privacy intact.
Why This Matters to You
Transparency: You can independently verify every transaction, ensuring that no unauthorized actions were taken with your funds.
Security: Your transactions are protected by cryptographic proof, meaning they cannot be altered without detection.
Efficiency: Instead of costly, slow transactions flooding the blockchain, our rollup system ensures low-cost, fast verification.
Privacy: Transaction verification is done without exposing personal or sensitive information.
How It Works
Rails has on-chain custody and centralized order matching & transaction processing. To ensure integrity between these two systems, we need a reliable way to confirm that transaction data hasn’t been tampered with. To achieve this, we compute a cryptographic hash for each transaction and organize them into a Merkle tree—a specialized data structure that enables secure, efficient, and scalable validation of large data sets. The root hash of this tree is a single, unique value that represents the entire set of transaction hashes. If even one transaction changes, the root hash will also change. We then publish this root hash to the Ink blockchain, providing a public, tamper-evident record of the transaction set’s integrity.
Breaking It Down
Bundling Transactions: Rails central system batches individual transactions into a single block.
Creating a Unique Summary: The transactions are structured into a Merkle tree, which compresses them into a single summary called the Merkle root. The Merkle root, displayed as the Root Hash, acts as a fingerprint for the block, uniquely identifying all transactions. Along with the root hash is the sum total of all fees and withdrawals included in the block
Submitting to the Blockchain: Instead of submitting every transaction separately, only the Merkle root is published on the blockchain. This makes the process more efficient while maintaining anonymity of user data to avoid trade front running. We also submit the latest root hash to our Smart Contract.
Verifying the Transactions: To validate a transaction, the “Validate Block” button applies each transaction hash in the block to the Merkle tree algorithm, which then generates the root hash. If this matches the established root hash, you can be confident that no transactions in that block have been altered.
Last updated
Was this helpful?