← previous blocknext block →recent activity
Analyzing
Block #105,841,168
38 transactions · 34 stateful · 2026-09-18 08:16:28 UTC
Parallelism
79/100
Blocked
53%
Avg conflicts / tx
1.32
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #105,841,168 · 38 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
1w02w13w24w37w08w09w110w212w113w220w124w426w327w328w429w530w631w737w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb482658a…e4f5
0x34b655…2a6f
14 touches
21 conflicts
0xe9c367cd…30a9
0x34b655…2a6f
12 touches
15 conflicts
0xac2a0273…721b
0x34b655…2a6f
10 touches
10 conflicts
0x4ec9ff52…e6f7
0x34b655…2a6f
8 touches
6 conflicts
0x737acb78…fce8
0x34b655…2a6f
8 touches
6 conflicts
0x15337d62…cf68
0xd32edf…ff58
7 touches
6 conflicts
0xd53220ed…473b
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
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
21 conflicts on slot 0xb482658a15…f3e4f5
Audit this contract →
← previous block·next block →recent activity