← previous blocknext block →recent activity
Analyzing
Block #106,328,454
24 transactions · 22 stateful · 2026-09-20 01:10:06 UTC
Parallelism
79/100
Blocked
45%
Avg conflicts / tx
0.96
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,328,454 · 24 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w17w211w212w314w015w116w217w318w420w321w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x0f7c4acb…e894
0x6f6493…b480
10 touches
10 conflicts
0x116011e5…9775
0x6f6493…b480
10 touches
10 conflicts
0x23bca02b…393d
0x6f6493…b480
10 touches
10 conflicts
0x23c2e565…acd5
0x6f6493…b480
10 touches
10 conflicts
0x2822911f…0128
0x6f6493…b480
10 touches
10 conflicts
0x3b356c5d…0a89
0x6f6493…b480
10 touches
10 conflicts
0x3b58b211…33df
0x6f6493…b480
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
10 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity