← previous blocknext block →recent activity
Analyzing
Block #99,880,530
34 transactions · 26 stateful · 2026-08-28 10:58:24 UTC
Parallelism
85/100
Blocked
35%
Avg conflicts / tx
0.41
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #99,880,530 · 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
1w05w06w17w210w112w313w016w117w419w025w029w130w233w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2892c5fe…9b5e
0xd32edf…ff58
7 touches
6 conflicts
0x11258774…9892
0x2a68ba…90c5
4 touches
1 conflict
0x6324ccc9…14fd
0x34b655…2a6f
4 touches
1 conflict
0x6d1b72ee…6b78
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xf6cc7de8…0b4a
0x3bd359…433a
4 touches
1 conflict
0x00000000…0000
0x63e48b…53f2
4 touches
1 conflict
0x17606ba6…1b6e
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 0x2892c5fedc…789b5e
Audit this contract →
← previous block·next block →recent activity