← previous blocknext block →recent activity
Analyzing
Block #99,255,960
25 transactions · 19 stateful · 2026-08-26 06:21:08 UTC
Parallelism
68/100
Blocked
53%
Avg conflicts / tx
1.28
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #99,255,960 · 25 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w05w110w111w212w214w315w416w517w523w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x497d19bc…865e
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0x737acb78…fce8
0x34b655…2a6f
10 touches
10 conflicts
0xac2a0273…721b
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x7de57974…f5ba
0x34b655…2a6f
8 touches
6 conflicts
0xd33e2f5b…9bfd
0x34b655…2a6f
7 touches
6 conflicts
0x6713b018…05f3
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
10 conflicts on slot 0x497d19bc5c…95865e
Audit this contract →
← previous block·next block →recent activity