← previous blocknext block →recent activity
Analyzing
Block #98,089,649
35 transactions · 29 stateful · 2026-08-22 03:49:19 UTC
Parallelism
89/100
Blocked
41%
Avg conflicts / tx
0.49
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #98,089,649 · 35 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w16w08w010w112w013w114w015w116w017w120w221w322w024w125w027w231w232w334w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc057236f…5104
0xd32edf…ff58
7 touches
6 conflicts
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…001c
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002c
0x1b6862…e19c
4 touches
1 conflict
0x9b334941…fdde
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
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
6 conflicts on slot 0xc057236f2c…aa5104
Audit this contract →
← previous block·next block →recent activity