← previous blocknext block →recent activity
Analyzing
Block #106,917,611
26 transactions · 24 stateful · 2026-09-22 02:36:23 UTC
Parallelism
69/100
Blocked
58%
Avg conflicts / tx
1.35
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,917,611 · 26 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
1w02w13w25w06w17w28w310w211w312w413w514w615w720w325w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x69411fb3…e36d
0x34b655…2a6f
14 touches
21 conflicts
0xe720a4c6…8eb0
0x34b655…2a6f
12 touches
15 conflicts
0x91685a55…a18b
0x34b655…2a6f
12 touches
15 conflicts
0xf71016c7…5c7c
0x34b655…2a6f
8 touches
6 conflicts
0x0463db49…5d05
0x34b655…2a6f
8 touches
6 conflicts
0x42522e76…2592
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…002d
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
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
21 conflicts on slot 0x69411fb3ba…bce36d
Audit this contract →
← previous block·next block →recent activity