← previous blocknext block →recent activity
Analyzing
Block #99,019,253
30 transactions · 25 stateful · 2026-08-25 10:25:17 UTC
Parallelism
70/100
Blocked
56%
Avg conflicts / tx
1.4
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #99,019,253 · 30 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w28w09w110w311w012w113w214w315w416w518w625w727w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0163ee78…1e67
0xd32edf…ff58
15 touches
28 conflicts
0xe5cc66e7…2fbf
0x065c9d…c394
7 touches
6 conflicts
0x11258774…9892
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x5c8c6ab6…dc36
0x065c9d…c394
6 touches
3 conflicts
0xadac4a86…c2bc
0x34b655…2a6f
6 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0xe870e232…7369
0xf9b0c8…8081
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
28 conflicts on slot 0x0163ee7889…dd1e67
Audit this contract →
← previous block·next block →recent activity