← previous blocknext block →recent activity
Analyzing
Block #102,877,966
24 transactions · 18 stateful · 2026-09-07 22:55:26 UTC
Parallelism
79/100
Blocked
44%
Avg conflicts / tx
0.63
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #102,877,966 · 24 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
1w03w16w17w110w213w314w015w116w222w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe1d7280a…0db3
0xd32edf…ff58
9 touches
10 conflicts
0xd17580f9…ece1
0x754704…b603
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001c
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002c
0x1b6862…e19c
4 touches
1 conflict
0x0f94ee4c…189b
0x1b6862…e19c
4 touches
1 conflict
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…004b
0x80c745…7210
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 0xe1d7280a52…630db3
Audit this contract →
← previous block·next block →recent activity