Getting Started

Watch transactions compete for shared accounts using different concurrency control strategies.

Pessimistic Mode

User specifies all conflicting transactions upfront. Transactions are organized into sequential batches (consecutive IDs only, e.g., T2→T3→T4). Each transaction accesses ALL needed accounts at once, executes, then commits atomically (all-or-nothing).

Transaction States

Waiting
Executing
Rerunning
Completed
Exclusive Access (ON): All account access is exclusive. Conflicts occur when two or more transactions read or write to a shared account.
Transaction Conflicts: Click this button to view and edit which accounts each transaction reads or writes. Customize transaction dependencies before running the simulation.

Statistics

Completed: 0 / 10
Active: 0
Waiting: 0
Retries: 0
Time: 0.0s
Step 1 of 7