← previous blocknext block →recent activity
Analyzing
Block #106,189,165
24 transactions · 24 stateful · 2026-09-19 13:29:03 UTC
Parallelism
58/100
Blocked
67%
Avg conflicts / tx
2.04
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #106,189,165 · 24 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w06w18w19w210w311w412w513w614w715w816w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbf5419db…6b18
0x34b655…2a6f
14 touches
21 conflicts
0xab981df1…2941
0x34b655…2a6f
10 touches
10 conflicts
0xd17580f9…ece1
0x754704…b603
10 touches
10 conflicts
0x6b267bdf…b173
0x34b655…2a6f
10 touches
10 conflicts
0xd41f5136…97c6
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x67a56c8b…f955
0x34b655…2a6f
8 touches
6 conflicts
0x1b25f260…c429
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 0xbf5419db18…726b18
Audit this contract →
← previous block·next block →recent activity