← previous blocknext block →recent activity
Analyzing
Block #106,215,520
32 transactions · 32 stateful · 2026-09-19 15:41:44 UTC
Parallelism
75/100
Blocked
66%
Avg conflicts / tx
1.72
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,215,520 · 32 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w08w09w112w013w414w116w217w318w119w426w128w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0xe7fe4913…841d
0xd32edf…ff58
11 touches
15 conflicts
0xd17580f9…ece1
0x754704…b603
10 touches
10 conflicts
0x1b501ca7…3852
0x34b655…2a6f
10 touches
10 conflicts
0x98067f20…59ea
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
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 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity