← previous blocknext block →recent activity
Analyzing
Block #106,370,925
23 transactions · 21 stateful · 2026-09-20 04:43:51 UTC
Parallelism
57/100
Blocked
62%
Avg conflicts / tx
1.91
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #106,370,925 · 23 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w15w29w310w414w215w516w317w618w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5229ae5f…473c
0x34b655…2a6f
10 touches
10 conflicts
0x0dd3d3cd…7281
0x34b655…2a6f
10 touches
10 conflicts
0x9dd0a735…4d04
0x34b655…2a6f
10 touches
10 conflicts
0xd563f3a1…94b1
0x34b655…2a6f
10 touches
10 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
8 touches
6 conflicts
0x1b25f260…c429
0x34b655…2a6f
8 touches
6 conflicts
0x2686eb58…7c02
0x34b655…2a6f
8 touches
6 conflicts
0x7cd9fd28…a158
0x34b655…2a6f
8 touches
6 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 0x5229ae5fa3…b6473c
Audit this contract →
← previous block·next block →recent activity