← previous blocknext block →recent activity
Analyzing
Block #106,568,571
30 transactions · 29 stateful · 2026-09-20 21:18:37 UTC
Parallelism
83/100
Blocked
45%
Avg conflicts / tx
0.9
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,568,571 · 30 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w15w210w012w114w015w216w317w318w419w123w128w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x54f7f60f…43cc
0x34b655…2a6f
8 touches
6 conflicts
0x1b25f260…c429
0x34b655…2a6f
8 touches
6 conflicts
0x5e2ea201…12de
0x34b655…2a6f
8 touches
6 conflicts
0x17cf4141…d6c1
0x34b655…2a6f
8 touches
6 conflicts
0x9b96d962…259e
0x34b655…2a6f
8 touches
6 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
8 touches
6 conflicts
0x3b6e959d…158f
0x34b655…2a6f
8 touches
6 conflicts
0xea5e1b8c…3eb0
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
6 conflicts on slot 0x54f7f60f23…cb43cc
Audit this contract →
← previous block·next block →recent activity