← previous blocknext block →recent activity
Analyzing
Block #99,991,911
30 transactions · 28 stateful · 2026-08-28 20:19:39 UTC
Parallelism
80/100
Blocked
46%
Avg conflicts / tx
1
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #99,991,911 · 30 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
1w02w13w24w05w06w18w39w110w011w113w315w417w523w224w425w527w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcc494d2e…3535
0xd32edf…ff58
11 touches
15 conflicts
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0xfcb7b8b2…ebb3
0x065c9d…c394
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001a
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002a
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: FastLane: FastLaneAuctionHandler
15 conflicts on slot 0xcc494d2ec6…6e3535
Audit this contract →
← previous block·next block →recent activity