← previous blocknext block →recent activity
Analyzing
Block #106,394,968
24 transactions · 24 stateful · 2026-09-20 06:44:52 UTC
Parallelism
54/100
Blocked
63%
Avg conflicts / tx
2.5
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #106,394,968 · 24 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w15w06w18w211w312w413w514w615w716w817w918w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd1ed6c82…869d
0x34b655…2a6f
16 touches
28 conflicts
0xd563f3a1…94b1
0x34b655…2a6f
16 touches
28 conflicts
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0xc8e54058…6a98
0x34b655…2a6f
12 touches
15 conflicts
0x9ff4ca89…6115
0x34b655…2a6f
10 touches
10 conflicts
0xac0b4a08…faae
0x34b655…2a6f
10 touches
10 conflicts
0x8590b692…b267
0x34b655…2a6f
10 touches
10 conflicts
0x07610b8e…6093
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
28 conflicts on slot 0xd1ed6c827e…c8869d
Audit this contract →
← previous block·next block →recent activity