← previous blocknext block →recent activity
Analyzing
Block #99,875,970
36 transactions · 29 stateful · 2026-08-28 10:35:25 UTC
Parallelism
72/100
Blocked
59%
Avg conflicts / tx
1.58
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #99,875,970 · 36 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
1w02w13w24w38w213w414w515w419w620w722w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xabbd40fc…83a0
0xd32edf…ff58
17 touches
36 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…0018
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0028
0x1b6862…e19c
8 touches
6 conflicts
0xac79a0c7…be0f
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
36 conflicts on slot 0xabbd40fc6f…ab83a0
Audit this contract →
← previous block·next block →recent activity