← previous blocknext block →recent activity
Analyzing
Block #102,856,286
25 transactions · 17 stateful · 2026-09-07 21:06:21 UTC
Parallelism
80/100
Blocked
53%
Avg conflicts / tx
0.6
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #102,856,286 · 25 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
2w03w110w211w312w114w016w417w018w119w020w121w122w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe537a6c9…8c33
0xd32edf…ff58
9 touches
10 conflicts
0x00000000…002c
0x1b6862…e19c
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x09106a95…1467
0x33176b…e078
4 touches
1 conflict
0x0d03bddb…6658
0x34b655…2a6f
4 touches
1 conflict
0x7862fbce…d1a5
0x34b655…2a6f
4 touches
1 conflict
0x626418b6…20b6
0x3bd359…433a
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
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 0xe537a6c967…828c33
Audit this contract →
← previous block·next block →recent activity