← previous blocknext block →recent activity
Analyzing
Block #99,475,797
25 transactions · 25 stateful · 2026-08-27 00:47:50 UTC
Parallelism
68/100
Blocked
32%
Avg conflicts / tx
0.72
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #99,475,797 · 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
1w02w13w27w28w311w412w514w615w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb1856468…e84f
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xb6ed511f…6b68
0x34b655…2a6f
8 touches
6 conflicts
0x9e0d3033…198e
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0028
0x1b6862…e19c
6 touches
3 conflicts
0xb538c6fa…9ae5
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x5f88acf6…d385
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 0xb185646883…2ae84f
Audit this contract →
← previous block·next block →recent activity