← previous blocknext block →recent activity
Analyzing
Block #106,371,060
29 transactions · 27 stateful · 2026-09-20 04:44:32 UTC
Parallelism
62/100
Blocked
70%
Avg conflicts / tx
2
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #106,371,060 · 29 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w26w37w48w59w610w712w217w824w326w127w928w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8d664414…3344
0x34b655…2a6f
16 touches
28 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x482471ad…122f
0x34b655…2a6f
12 touches
15 conflicts
0x9dd0a735…4d04
0x34b655…2a6f
8 touches
6 conflicts
0x1b662182…c900
0x34b655…2a6f
8 touches
6 conflicts
0x5229ae5f…473c
0x34b655…2a6f
8 touches
6 conflicts
0x465d39d6…9fc0
0x34b655…2a6f
8 touches
6 conflicts
0x8944bfee…f2d2
0xd32edf…ff58
7 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
28 conflicts on slot 0x8d664414de…103344
Audit this contract →
← previous block·next block →recent activity