← previous blocknext block →recent activity
Analyzing
Block #105,853,258
34 transactions · 32 stateful · 2026-09-18 09:17:28 UTC
Parallelism
68/100
Blocked
53%
Avg conflicts / tx
2.06
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #105,853,258 · 34 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
1w02w13w24w35w48w09w118w222w523w624w725w826w927w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
16 touches
28 conflicts
0xe3a467d1…c539
0x34b655…2a6f
16 touches
28 conflicts
0x55192654…91fe
0x34b655…2a6f
16 touches
28 conflicts
0x489d7033…e8e1
0x34b655…2a6f
12 touches
15 conflicts
0x00000000…002f
0x1b6862…e19c
10 touches
10 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
10 touches
10 conflicts
0xdbc6e634…e16c
0x1b6862…e19c
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
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 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity