← previous blocknext block →recent activity
Analyzing
Block #107,824,265
29 transactions · 24 stateful · 2026-09-25 06:42:21 UTC
Parallelism
83/100
Blocked
42%
Avg conflicts / tx
0.62
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #107,824,265 · 29 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w48w09w314w017w118w219w020w123w024w128w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb64c8f20…a80e
0xd32edf…ff58
9 touches
10 conflicts
0x1f8a126c…9aa8
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001f
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002f
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
10 conflicts on slot 0xb64c8f20d9…c5a80e
Audit this contract →
← previous block·next block →recent activity