← previous blocknext block →recent activity
Analyzing
Block #106,420,411
33 transactions · 31 stateful · 2026-09-20 08:52:54 UTC
Parallelism
55/100
Blocked
58%
Avg conflicts / tx
2.76
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #106,420,411 · 33 txs across 15 waves · depth 15
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w26w37w313w414w516w317w618w722w823w924w925w1026w1127w1231w13
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbe9d1d23…3de2
0x34b655…2a6f
24 touches
66 conflicts
0x3d52cd2f…38f9
0x34b655…2a6f
18 touches
36 conflicts
0xc824469a…6425
0x34b655…2a6f
16 touches
28 conflicts
0x482471ad…122f
0x34b655…2a6f
14 touches
21 conflicts
0x24442cb9…eaa1
0x34b655…2a6f
10 touches
10 conflicts
0x310a7246…2dcb
0x34b655…2a6f
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x7cd9fd28…a158
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
66 conflicts on slot 0xbe9d1d2362…0d3de2
Audit this contract →
← previous block·next block →recent activity