← previous blocknext block →recent activity
Analyzing
Block #99,985,801
21 transactions · 21 stateful · 2026-08-28 19:48:50 UTC
Parallelism
67/100
Blocked
57%
Avg conflicts / tx
1
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #99,985,801 · 21 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
1w02w13w25w06w17w29w010w111w212w313w414w216w517w618w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf06fce24…887d
0x34b655…2a6f
8 touches
6 conflicts
0x07bb3f5a…617e
0x34b655…2a6f
8 touches
6 conflicts
0x42522e76…2592
0x34b655…2a6f
8 touches
6 conflicts
0x6dedaff6…161b
0x34b655…2a6f
8 touches
6 conflicts
0x7d499bce…b0ea
0x34b655…2a6f
8 touches
6 conflicts
0xa5977596…ddee
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xd9f18d9a…141d
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
6 conflicts on slot 0xf06fce24b3…55887d
Audit this contract →
← previous block·next block →recent activity