← previous blocknext block →recent activity
Analyzing
Block #102,190,083
25 transactions · 24 stateful · 2026-09-05 12:55:26 UTC
Parallelism
68/100
Blocked
54%
Avg conflicts / tx
1.44
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #102,190,083 · 25 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w04w15w26w37w48w116w523w624w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x66f3c985…854f
0xd32edf…ff58
15 touches
28 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x846f2172…fd54
0x0555e3…2b9c
4 touches
1 conflict
0x18e86f02…fa98
0x34b655…2a6f
4 touches
1 conflict
0xc5cfc032…d3bd
0x34b655…2a6f
4 touches
1 conflict
0xd66696e0…0842
0x34b655…2a6f
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
28 conflicts on slot 0x66f3c9850c…c0854f
Audit this contract →
← previous block·next block →recent activity