← previous blocknext block →recent activity
Analyzing
Block #99,938,769
40 transactions · 36 stateful · 2026-08-28 15:51:53 UTC
Parallelism
80/100
Blocked
53%
Avg conflicts / tx
1.13
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #99,938,769 · 40 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w06w28w312w117w318w419w520w625w732w335w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbbdbcf35…a8e3
0xd32edf…ff58
15 touches
28 conflicts
0x5f77d607…2c84
0x065c9d…c394
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0019
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0029
0x1b6862…e19c
6 touches
3 conflicts
0x394c3833…b4a8
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
28 conflicts on slot 0xbbdbcf351f…bba8e3
Audit this contract →
← previous block·next block →recent activity