← previous blocknext block →recent activity
Analyzing
Block #102,048,865
20 transactions · 20 stateful · 2026-09-05 00:59:26 UTC
Parallelism
70/100
Blocked
65%
Avg conflicts / tx
1.6
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #102,048,865 · 20 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w06w17w38w49w010w111w212w314w415w517w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x482471ad…122f
0x34b655…2a6f
12 touches
15 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
10 touches
10 conflicts
0xbed56808…7af0
0x065c9d…c394
8 touches
6 conflicts
0x91b13e91…855d
0x34b655…2a6f
8 touches
6 conflicts
0xd66696e0…0842
0x34b655…2a6f
8 touches
6 conflicts
0xb6f93385…f677
0xd32edf…ff58
7 touches
6 conflicts
0x948836ff…59ab
0x34b655…2a6f
6 touches
4 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 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity