← previous blocknext block →recent activity
Analyzing
Block #106,422,251
23 transactions · 22 stateful · 2026-09-20 09:02:09 UTC
Parallelism
65/100
Blocked
59%
Avg conflicts / tx
1.43
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,422,251 · 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
1w02w13w24w15w26w27w38w310w411w414w515w618w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf35d33d9…129b
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x4188cc5f…2d2e
0x34b655…2a6f
8 touches
6 conflicts
0xef8ae70c…e193
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x93afca4c…b47b
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
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
10 conflicts on slot 0xf35d33d9c5…27129b
Audit this contract →
← previous block·next block →recent activity