← previous blocknext block →recent activity
Analyzing
Block #106,422,717
27 transactions · 26 stateful · 2026-09-20 09:04:30 UTC
Parallelism
63/100
Blocked
58%
Avg conflicts / tx
1.81
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #106,422,717 · 27 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
1w02w13w24w35w46w57w68w719w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3b53436c…2ec3
0x34b655…2a6f
18 touches
36 conflicts
0x1b4318f0…78fb
0x34b655…2a6f
12 touches
15 conflicts
0x5e3014f0…b4e1
0x34b655…2a6f
10 touches
10 conflicts
0x48203298…65cb
0x34b655…2a6f
10 touches
10 conflicts
0x53c0da93…c395
0x34b655…2a6f
8 touches
6 conflicts
0x2e062645…2181
0x34b655…2a6f
8 touches
6 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
8 touches
6 conflicts
0x1b25f260…c429
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 0x3b53436c6f…c62ec3
Audit this contract →
← previous block·next block →recent activity