← previous blocknext block →recent activity
Analyzing
Block #106,186,821
25 transactions · 24 stateful · 2026-09-19 13:17:15 UTC
Parallelism
72/100
Blocked
54%
Avg conflicts / tx
1.32
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,186,821 · 25 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w05w26w38w211w012w113w214w315w416w517w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x80fdc5be…7070
0x34b655…2a6f
12 touches
15 conflicts
0x07c47b1c…93c8
0x34b655…2a6f
12 touches
15 conflicts
0xec2a8d79…70cb
0x34b655…2a6f
8 touches
6 conflicts
0xd17580f9…ece1
0x754704…b603
8 touches
6 conflicts
0xd597209e…9800
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x18cf3003…51d1
0x065c9d…c394
6 touches
3 conflicts
0x74200327…23ac
0x34b655…2a6f
4 touches
1 conflict
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
15 conflicts on slot 0x80fdc5be8d…527070
Audit this contract →
← previous block·next block →recent activity