← previous blocknext block →recent activity
Analyzing
Block #99,880,513
20 transactions · 19 stateful · 2026-08-28 10:58:19 UTC
Parallelism
80/100
Blocked
47%
Avg conflicts / tx
0.75
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #99,880,513 · 20 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
1w02w03w14w25w36w07w110w011w212w315w116w218w019w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x05a5921e…7121
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…0002
0xf5b5f7…6d70
6 touches
3 conflicts
0x71b395d9…1697
0x34b655…2a6f
6 touches
3 conflicts
0x029a5d2e…2bce
0x34b655…2a6f
4 touches
1 conflict
0x997ccc40…4dfd
0x3bd359…433a
4 touches
1 conflict
0xe2745681…ff50
0x3bd359…433a
4 touches
1 conflict
0x0b552eae…fbd9
0x754704…b603
4 touches
1 conflict
0x13477596…b14c
0x754704…b603
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 0x05a5921ed7…887121
Audit this contract →
← previous block·next block →recent activity