← previous blocknext block →recent activity
Analyzing
Block #96,129,743
20 transactions · 14 stateful · 2026-08-15 06:17:20 UTC
Parallelism
65/100
Blocked
57%
Avg conflicts / tx
1.15
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #96,129,743 · 20 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
1w02w13w24w35w48w09w110w514w615w017w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x99afd6b0…e139
0xd32edf…ff58
13 touches
21 conflicts
0x9885a25f…292b
0x1b6862…e19c
4 touches
1 conflict
0xf6cc7de8…0b4a
0x3bd359…433a
4 touches
1 conflict
0x00000000…0000
0x63e48b…53f2
4 touches
1 conflict
0x00000000…0003
0x63e48b…53f2
4 touches
1 conflict
0x00000000…0004
0x63e48b…53f2
4 touches
1 conflict
0x9a555477…19a8
0x754704…b603
4 touches
1 conflict
0x00000000…0012
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
21 conflicts on slot 0x99afd6b097…43e139
Audit this contract →
← previous block·next block →recent activity