← previous blocknext block →recent activity
Analyzing
Block #106,373,000
23 transactions · 22 stateful · 2026-09-20 04:54:18 UTC
Parallelism
74/100
Blocked
59%
Avg conflicts / tx
1.3
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,373,000 · 23 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w26w311w314w415w519w320w521w422w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0262e1c6…52e1
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xc9a6e112…69cc
0x34b655…2a6f
8 touches
6 conflicts
0xc96ccb33…491f
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x88fb7f79…26f4
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…002a
0x1b6862…e19c
6 touches
3 conflicts
0x4e7eb462…b2ac
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 0x0262e1c696…e752e1
Audit this contract →
← previous block·next block →recent activity