← previous blocknext block →recent activity
Analyzing
Block #102,250,290
23 transactions · 22 stateful · 2026-09-05 18:00:27 UTC
Parallelism
70/100
Blocked
45%
Avg conflicts / tx
1.26
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #102,250,290 · 23 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w29w010w111w212w313w417w519w620w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x923e6c2a…b1ab
0x34b655…2a6f
12 touches
15 conflicts
0x482471ad…122f
0x34b655…2a6f
12 touches
15 conflicts
0x08399ab6…0057
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0xd66696e0…0842
0x34b655…2a6f
10 touches
10 conflicts
0x948836ff…59ab
0x34b655…2a6f
8 touches
6 conflicts
0x461f7d91…c43b
0x34b655…2a6f
7 touches
6 conflicts
0x00000000…0012
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
15 conflicts on slot 0x923e6c2a42…bfb1ab
Audit this contract →
← previous block·next block →recent activity