← previous blocknext block →recent activity
Analyzing
Block #98,355,748
34 transactions · 24 stateful · 2026-08-23 02:08:48 UTC
Parallelism
85/100
Blocked
33%
Avg conflicts / tx
0.38
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #98,355,748 · 34 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
1w05w08w113w214w015w117w118w319w423w028w132w033w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0050b648…fd7f
0xd32edf…ff58
7 touches
6 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x6fef9b92…89a2
0x065c9d…c394
6 touches
3 conflicts
0xea02471d…1539
0x34b655…2a6f
4 touches
1 conflict
0x17606ba6…1b6e
0x754704…b603
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x5ce08c09…7f3e
0xa6afd3…d132
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 0x0050b64850…f3fd7f
Audit this contract →
← previous block·next block →recent activity