← previous blocknext block →recent activity
Analyzing
Block #106,337,001
36 transactions · 34 stateful · 2026-09-20 01:53:07 UTC
Parallelism
56/100
Blocked
62%
Avg conflicts / tx
2.25
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #106,337,001 · 36 txs across 16 waves · depth 16
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w28w116w317w420w523w625w729w930w1033w13
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
16 touches
28 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
16 touches
28 conflicts
0x482471ad…122f
0x34b655…2a6f
14 touches
21 conflicts
0x9ba10aad…9bc5
0x34b655…2a6f
10 touches
10 conflicts
0x5f64f51c…9b23
0xd32edf…ff58
9 touches
10 conflicts
0x532f9f4c…8ca8
0x34b655…2a6f
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x0d72fcee…4b28
0x34b655…2a6f
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
28 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity