← previous blocknext block →recent activity
Analyzing
Block #106,422,404
13 transactions · 13 stateful · 2026-09-20 09:02:55 UTC
Parallelism
62/100
Blocked
62%
Avg conflicts / tx
1.46
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,422,404 · 13 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
1w02w13w25w26w37w38w410w411w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x49b9fdd5…9c16
0x34b655…2a6f
8 touches
6 conflicts
0x5e3014f0…b4e1
0x34b655…2a6f
8 touches
6 conflicts
0xa5811d93…8c73
0x34b655…2a6f
8 touches
6 conflicts
0x20994928…2ff8
0x34b655…2a6f
8 touches
6 conflicts
0x48203298…65cb
0x34b655…2a6f
8 touches
6 conflicts
0xedf0fd5d…0c8b
0x34b655…2a6f
6 touches
3 conflicts
0x21b674ba…b82b
0x34b655…2a6f
6 touches
3 conflicts
0xd7668c61…55f8
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
6 conflicts on slot 0x49b9fdd5ff…6f9c16
Audit this contract →
← previous block·next block →recent activity