← previous blocknext block →recent activity
Analyzing
Block #99,076,694
40 transactions · 35 stateful · 2026-08-25 15:18:48 UTC
Parallelism
68/100
Blocked
80%
Avg conflicts / tx
2.6
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #99,076,694 · 40 txs across 13 waves · depth 13
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w48w215w516w617w718w824w925w1026w11
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8602f511…92ff
0xd32edf…ff58
23 touches
66 conflicts
0x00000000…0012
0x1b6862…e19c
16 touches
28 conflicts
0x00000000…0013
0x1b6862…e19c
16 touches
28 conflicts
0x00000000…0015
0x1b6862…e19c
16 touches
28 conflicts
0x00000000…0018
0x1b6862…e19c
16 touches
28 conflicts
0x00000000…0028
0x1b6862…e19c
16 touches
28 conflicts
0xf8480e2a…dfee
0x1b6862…e19c
16 touches
28 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
16 touches
28 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
66 conflicts on slot 0x8602f5112b…b192ff
Audit this contract →
← previous block·next block →recent activity