← previous blocknext block →recent activity
Analyzing
Block #106,420,453
21 transactions · 19 stateful · 2026-09-20 08:53:06 UTC
Parallelism
71/100
Blocked
47%
Avg conflicts / tx
1
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,420,453 · 21 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w510w011w112w216w217w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0eb62008…7585
0x34b655…2a6f
12 touches
15 conflicts
0x5e1c23e9…4f81
0x34b655…2a6f
12 touches
15 conflicts
0x310a7246…2dcb
0x34b655…2a6f
8 touches
6 conflicts
0x80398c66…f3cc
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x045532dd…4b7d
0x34b655…2a6f
6 touches
3 conflicts
0x1b25f260…c429
0x34b655…2a6f
6 touches
3 conflicts
0x51fc8795…126f
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 0x0eb62008d4…747585
Audit this contract →
← previous block·next block →recent activity