← previous blocknext block →recent activity
Analyzing
Block #106,468,205
21 transactions · 20 stateful · 2026-09-20 12:53:29 UTC
Parallelism
71/100
Blocked
55%
Avg conflicts / tx
1.29
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,468,205 · 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
1w02w03w14w25w37w08w111w212w315w416w517w418w520w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6af2981e…5a35
0x34b655…2a6f
12 touches
15 conflicts
0x30ceaa11…f481
0x34b655…2a6f
8 touches
6 conflicts
0xad862891…5d02
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xe098738f…9bbe
0x34b655…2a6f
6 touches
3 conflicts
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0xec2a8d79…70cb
0x34b655…2a6f
6 touches
3 conflicts
0x159cff26…7665
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 0x6af2981ee3…e95a35
Audit this contract →
← previous block·next block →recent activity