← previous blocknext block →recent activity
Analyzing
Block #102,020,137
33 transactions · 24 stateful · 2026-09-04 22:33:57 UTC
Parallelism
88/100
Blocked
33%
Avg conflicts / tx
0.42
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #102,020,137 · 33 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
3w08w09w110w214w115w216w017w126w331w332w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6a4cff6e…6537
0xd32edf…ff58
7 touches
6 conflicts
0x65903ef9…2567
0x34b655…2a6f
6 touches
3 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001b
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
6 conflicts on slot 0x6a4cff6e0a…7d6537
Audit this contract →
← previous block·next block →recent activity