← previous blocknext block →recent activity
Analyzing
Block #99,254,110
32 transactions · 30 stateful · 2026-08-26 06:11:49 UTC
Parallelism
75/100
Blocked
57%
Avg conflicts / tx
1.28
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #99,254,110 · 32 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
1w03w15w26w37w49w110w511w619w520w726w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa3635406…757d
0xd32edf…ff58
13 touches
21 conflicts
0x889d5e90…929a
0x2a68ba…90c5
10 touches
10 conflicts
0x00000000…0012
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0013
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0015
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…001b
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…002b
0x1b6862…e19c
10 touches
10 conflicts
0xc0f29314…17fa
0x1b6862…e19c
10 touches
10 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
21 conflicts on slot 0xa363540634…2e757d
Audit this contract →
← previous block·next block →recent activity