← previous blocknext block →recent activity
Analyzing
Block #107,813,261
35 transactions · 25 stateful · 2026-09-25 05:46:58 UTC
Parallelism
77/100
Blocked
52%
Avg conflicts / tx
1.09
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #107,813,261 · 35 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w110w212w317w118w219w320w421w522w623w732w333w434w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xba522812…1f1f
0x34b655…2a6f
16 touches
28 conflicts
0x3aff72dc…a704
0x34b655…2a6f
16 touches
28 conflicts
0x3d93ad2c…e747
0x34b655…2a6f
10 touches
10 conflicts
0x48203298…65cb
0x34b655…2a6f
10 touches
10 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0xc64d3656…0c1c
0x34b655…2a6f
8 touches
6 conflicts
0x429c8b35…0f5c
0x34b655…2a6f
8 touches
6 conflicts
0x49890ced…6f23
0x34b655…2a6f
8 touches
6 conflicts
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: Perpl
28 conflicts on slot 0xba52281226…3a1f1f
Audit this contract →
← previous block·next block →recent activity