← previous blocknext block →recent activity
Analyzing
Block #99,240,946
20 transactions · 19 stateful · 2026-08-26 05:05:36 UTC
Parallelism
85/100
Blocked
42%
Avg conflicts / tx
0.45
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #99,240,946 · 20 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w26w17w28w09w110w012w117w219w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x889fb203…8f55
0xd32edf…ff58
5 touches
3 conflicts
0x6d1795e3…1b0a
0x065c9d…c394
4 touches
1 conflict
0x01e7b865…6e6d
0x188d58…ea8e
4 touches
1 conflict
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…001b
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002b
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
3 conflicts on slot 0x889fb20320…f58f55
Audit this contract →
← previous block·next block →recent activity