← previous blocknext block →recent activity
Analyzing
Block #106,543,263
17 transactions · 16 stateful · 2026-09-20 19:11:15 UTC
Parallelism
59/100
Blocked
50%
Avg conflicts / tx
1.65
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,543,263 · 17 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w06w18w19w212w313w414w515w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdbf974a4…b232
0x34b655…2a6f
14 touches
21 conflicts
0xbec58cc5…9dbd
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0xb573813b…6c55
0x34b655…2a6f
10 touches
10 conflicts
0xf6deafb5…5c25
0x34b655…2a6f
8 touches
6 conflicts
0x4be9812b…48a9
0x34b655…2a6f
8 touches
6 conflicts
0xfa4c3219…d219
0x34b655…2a6f
6 touches
3 conflicts
0x1d9867ad…6d9a
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
21 conflicts on slot 0xdbf974a4cf…a9b232
Audit this contract →
← previous block·next block →recent activity