← previous blocknext block →recent activity
Analyzing
Block #106,376,750
27 transactions · 26 stateful · 2026-09-20 05:13:10 UTC
Parallelism
59/100
Blocked
58%
Avg conflicts / tx
1.3
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #106,376,750 · 27 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
1w02w13w04w15w07w28w09w110w311w412w516w617w220w721w822w925w626w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x610d1895…3985
0x34b655…2a6f
10 touches
10 conflicts
0x17bb579f…938c
0x34b655…2a6f
8 touches
6 conflicts
0x80398c66…f3cc
0x34b655…2a6f
8 touches
6 conflicts
0x47755f1b…bc75
0x34b655…2a6f
8 touches
6 conflicts
0xf773abe1…0f16
0xd32edf…ff58
7 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x1fb8364c…c10d
0x34b655…2a6f
6 touches
3 conflicts
0xcb45d9d6…cb82
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 0x610d189548…f03985
Audit this contract →
← previous block·next block →recent activity