← previous blocknext block →recent activity
Analyzing
Block #99,359,063
25 transactions · 20 stateful · 2026-08-26 15:00:00 UTC
Parallelism
84/100
Blocked
45%
Avg conflicts / tx
0.6
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #99,359,063 · 25 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w17w09w010w112w013w114w116w217w318w220w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4d6b5922…2bae
0xd32edf…ff58
7 touches
6 conflicts
0x02373c43…3cb3
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001e
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002e
0x1b6862…e19c
6 touches
3 conflicts
0x8d47c9a4…f120
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0012
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
6 conflicts on slot 0x4d6b5922ba…162bae
Audit this contract →
← previous block·next block →recent activity