← previous blocknext block →recent activity
Analyzing
Block #106,207,125
33 transactions · 29 stateful · 2026-09-19 14:59:29 UTC
Parallelism
70/100
Blocked
52%
Avg conflicts / tx
1.64
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #106,207,125 · 33 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w36w07w08w09w110w211w112w413w517w523w624w625w726w827w928w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd3b627bf…69d4
0x34b655…2a6f
16 touches
28 conflicts
0x15e313f3…9aa1
0x34b655…2a6f
14 touches
21 conflicts
0x4ec9ff52…e6f7
0x34b655…2a6f
10 touches
10 conflicts
0xfefb0189…f726
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x48a44e49…f190
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…0012
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
28 conflicts on slot 0xd3b627bf48…ee69d4
Audit this contract →
← previous block·next block →recent activity