← previous blocknext block →recent activity
Analyzing
Block #106,407,200
28 transactions · 26 stateful · 2026-09-20 07:46:24 UTC
Parallelism
64/100
Blocked
73%
Avg conflicts / tx
2.11
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #106,407,200 · 28 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
1w02w13w24w35w211w312w213w314w416w518w419w620w721w822w924w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc4fde8da…e180
0x34b655…2a6f
18 touches
36 conflicts
0xb1927b58…f161
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…001b
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002b
0x1b6862…e19c
8 touches
6 conflicts
0x58e06bab…34ce
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0x2c2761c0…476e
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
36 conflicts on slot 0xc4fde8da22…f9e180
Audit this contract →
← previous block·next block →recent activity