← previous blocknext block →recent activity
Analyzing
Block #106,567,824
40 transactions · 27 stateful · 2026-09-20 21:14:51 UTC
Parallelism
77/100
Blocked
52%
Avg conflicts / tx
0.93
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #106,567,824 · 40 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w07w08w110w111w012w113w220w121w222w223w324w428w532w633w734w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x57175d65…7633
0x34b655…2a6f
10 touches
10 conflicts
0xca841faa…486a
0x34b655…2a6f
10 touches
10 conflicts
0xe8aa9a1d…4b01
0xd32edf…ff58
7 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x1b25f260…c429
0x34b655…2a6f
6 touches
3 conflicts
0x1d9867ad…6d9a
0x34b655…2a6f
6 touches
3 conflicts
0x2aab0897…78f7
0x34b655…2a6f
6 touches
3 conflicts
0xcb45d9d6…cb86
0x1b6862…e19c
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
10 conflicts on slot 0x57175d650a…5a7633
Audit this contract →
← previous block·next block →recent activity