← previous blocknext block →recent activity
Analyzing
Block #106,413,482
22 transactions · 21 stateful · 2026-09-20 08:18:01 UTC
Parallelism
64/100
Blocked
48%
Avg conflicts / tx
1.45
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,413,482 · 22 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
1w02w13w04w15w26w37w48w59w610w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa36c0167…93b2
0x34b655…2a6f
16 touches
28 conflicts
0x8d664414…3344
0x34b655…2a6f
16 touches
28 conflicts
0x0505bae8…b4fb
0x34b655…2a6f
10 touches
10 conflicts
0xe283e878…7262
0x34b655…2a6f
10 touches
10 conflicts
0xfbdfbd74…fefc
0x34b655…2a6f
8 touches
6 conflicts
0x1b25f260…c429
0x34b655…2a6f
8 touches
6 conflicts
0x3080fd80…120a
0x34b655…2a6f
8 touches
6 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
8 touches
6 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 0xa36c016722…ce93b2
Audit this contract →
← previous block·next block →recent activity