← previous blocknext block →recent activity
Analyzing
Block #99,875,901
18 transactions · 16 stateful · 2026-08-28 10:35:04 UTC
Parallelism
72/100
Blocked
50%
Avg conflicts / tx
1
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #99,875,901 · 18 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w14w06w18w29w010w011w212w313w214w417w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fce7a05…d778
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x443a3e47…f4a4
0x065c9d…c394
6 touches
3 conflicts
0x278603a8…d824
0x34b655…2a6f
6 touches
3 conflicts
0xd5982776…4847
0x34b655…2a6f
6 touches
3 conflicts
0x9a8482cc…8bee
0x34b655…2a6f
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
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
10 conflicts on slot 0x6fce7a0516…35d778
Audit this contract →
← previous block·next block →recent activity