← previous blocknext block →recent activity
Analyzing
Block #106,377,325
23 transactions · 22 stateful · 2026-09-20 05:16:04 UTC
Parallelism
65/100
Blocked
55%
Avg conflicts / tx
1.7
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,377,325 · 23 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
1w02w13w05w26w38w110w311w413w415w416w517w618w722w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7ed0ea2d…0ae5
0x34b655…2a6f
14 touches
21 conflicts
0xc8cb0701…3926
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x54f7f60f…43cc
0x34b655…2a6f
6 touches
3 conflicts
0x92b49f44…ee4f
0x34b655…2a6f
6 touches
3 conflicts
0x80398c66…f3cc
0x34b655…2a6f
6 touches
3 conflicts
0x9ff4ca89…6115
0x34b655…2a6f
6 touches
3 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
21 conflicts on slot 0x7ed0ea2d6d…c30ae5
Audit this contract →
← previous block·next block →recent activity