← previous blocknext block →recent activity
Analyzing
Block #106,935,374
28 transactions · 26 stateful · 2026-09-22 04:05:47 UTC
Parallelism
68/100
Blocked
65%
Avg conflicts / tx
2.04
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #106,935,374 · 28 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
1w02w13w24w35w46w57w08w010w111w216w318w524w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x34c48330…703f
0x34b655…2a6f
12 touches
15 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x737fc355…d032
0xd32edf…ff58
11 touches
15 conflicts
0x9e92f2a4…342e
0x34b655…2a6f
10 touches
10 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0xf58eca50…59fb
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
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
15 conflicts on slot 0x34c4833013…14703f
Audit this contract →
← previous block·next block →recent activity