← previous blocknext block →recent activity
Analyzing
Block #106,215,997
25 transactions · 22 stateful · 2026-09-19 15:44:08 UTC
Parallelism
64/100
Blocked
68%
Avg conflicts / tx
1.88
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #106,215,997 · 25 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
1w02w13w24w35w46w510w315w317w418w419w520w621w722w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdf16ac33…3b1d
0x34b655…2a6f
16 touches
28 conflicts
0xecf22f58…5939
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0xdacdb48b…4a60
0xd32edf…ff58
11 touches
15 conflicts
0x00000000…002f
0x1b6862…e19c
10 touches
10 conflicts
0xba5743c7…21c6
0x1b6862…e19c
10 touches
10 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0012
0x1b6862…e19c
10 touches
10 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 0xdf16ac3345…b33b1d
Audit this contract →
← previous block·next block →recent activity