← previous blocknext block →recent activity
Analyzing
Block #102,550,745
27 transactions · 23 stateful · 2026-09-06 19:23:10 UTC
Parallelism
81/100
Blocked
52%
Avg conflicts / tx
0.78
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #102,550,745 · 27 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
2w03w14w15w211w212w314w318w220w321w423w024w125w226w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x566b2044…feed
0xd32edf…ff58
9 touches
10 conflicts
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001d
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002d
0x1b6862…e19c
4 touches
1 conflict
0x9b334941…fddf
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
10 conflicts on slot 0x566b2044cd…e8feed
Audit this contract →
← previous block·next block →recent activity