← previous blocknext block →recent activity
Analyzing
Block #106,053,181
20 transactions · 20 stateful · 2026-09-19 02:04:42 UTC
Parallelism
60/100
Blocked
60%
Avg conflicts / tx
2.05
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,053,181 · 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
1w02w13w04w16w07w19w210w111w212w313w414w515w616w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x49890ced…6f23
0x34b655…2a6f
10 touches
10 conflicts
0x2d071de0…c86e
0x34b655…2a6f
8 touches
6 conflicts
0x07c47b1c…93c8
0x34b655…2a6f
8 touches
6 conflicts
0xd29519c3…b8c2
0x34b655…2a6f
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0xdbc6e634…e168
0x1b6862…e19c
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
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
15 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity