← previous blocknext block →recent activity
Analyzing
Block #99,880,525
38 transactions · 31 stateful · 2026-08-28 10:58:22 UTC
Parallelism
82/100
Blocked
52%
Avg conflicts / tx
1.13
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #99,880,525 · 38 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
1w02w13w24w310w412w424w526w528w632w533w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0f6ddb5a…76aa
0xd32edf…ff58
13 touches
21 conflicts
0x00000000…0013
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0015
0x1b6862…e19c
10 touches
10 conflicts
0xd1480c90…ae04
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0028
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0xba38536d…2b7d
0x065c9d…c394
8 touches
6 conflicts
0x00000000…0012
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
21 conflicts on slot 0x0f6ddb5a92…d376aa
Audit this contract →
← previous block·next block →recent activity