← previous blocknext block →recent activity
Analyzing
Block #106,539,749
31 transactions · 31 stateful · 2026-09-20 18:53:34 UTC
Parallelism
71/100
Blocked
52%
Avg conflicts / tx
1.42
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #106,539,749 · 31 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w36w07w18w29w310w411w514w418w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc20768f8…d947
0x34b655…2a6f
14 touches
21 conflicts
0x735a86cd…b64d
0x34b655…2a6f
14 touches
21 conflicts
0x7d6b9af1…9a38
0x34b655…2a6f
8 touches
6 conflicts
0x1b25f260…c429
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x524f0872…0d12
0x34b655…2a6f
8 touches
6 conflicts
0x526ccad3…efbd
0xd32edf…ff58
7 touches
6 conflicts
0x3acc6a13…0f74
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 0xc20768f834…a4d947
Audit this contract →
← previous block·next block →recent activity