← previous blocknext block →recent activity
Analyzing
Block #99,116,445
25 transactions · 22 stateful · 2026-08-25 18:39:06 UTC
Parallelism
60/100
Blocked
64%
Avg conflicts / tx
2.04
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #99,116,445 · 25 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w37w38w49w510w611w715w816w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x86e3e76c…f3db
0xd32edf…ff58
19 touches
45 conflicts
0xa02838a3…bc54
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0019
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0029
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
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
45 conflicts on slot 0x86e3e76cba…98f3db
Audit this contract →
← previous block·next block →recent activity