← previous blocknext block →recent activity
Analyzing
Block #99,249,762
30 transactions · 26 stateful · 2026-08-26 05:49:56 UTC
Parallelism
77/100
Blocked
42%
Avg conflicts / tx
0.87
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #99,249,762 · 30 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w411w414w418w520w022w125w526w629w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x26ac4a2b…c232
0xd32edf…ff58
11 touches
15 conflicts
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…001b
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002b
0x1b6862…e19c
8 touches
6 conflicts
0x6b1259e6…4e10
0x1b6862…e19c
8 touches
6 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 0x26ac4a2bbc…13c232
Audit this contract →
← previous block·next block →recent activity