← previous blocknext block →recent activity
Analyzing
Block #106,429,687
20 transactions · 20 stateful · 2026-09-20 09:39:34 UTC
Parallelism
60/100
Blocked
60%
Avg conflicts / tx
2.25
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,429,687 · 20 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
1w02w13w24w35w26w37w410w412w413w515w617w718w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xba33378a…f1df
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0xec4ebaa6…7da8
0x34b655…2a6f
12 touches
15 conflicts
0x00000000…001b
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…002b
0x1b6862…e19c
10 touches
10 conflicts
0x11998eac…f9a2
0x1b6862…e19c
10 touches
10 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0012
0x1b6862…e19c
10 touches
10 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 0xba33378abc…73f1df
Audit this contract →
← previous block·next block →recent activity