← previous blocknext block →recent activity
Analyzing
Block #108,566,900
21 transactions · 19 stateful · 2026-09-27 21:00:16 UTC
Parallelism
86/100
Blocked
42%
Avg conflicts / tx
0.48
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #108,566,900 · 21 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w06w18w09w110w212w114w216w017w118w219w020w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3a663e9a…a9c5
0x508254…98bd
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x3a663e9a…a9c4
0x508254…98bd
6 touches
3 conflicts
0xcb45d9d6…cb86
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x3a663e9a…a9c6
0x508254…98bd
4 touches
1 conflict
0x3a663e9a…a9ca
0x508254…98bd
4 touches
1 conflict
What's blocking what?
Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.
The bottleneck
Throughput-killer: 0x508254c8…4a98bd
3 conflicts on slot 0x3a663e9a3a…2fa9c5
Audit this contract →
← previous block·next block →recent activity