← previous blocknext block →recent activity
Analyzing
Block #102,305,957
29 transactions · 27 stateful · 2026-09-05 22:42:30 UTC
Parallelism
79/100
Blocked
41%
Avg conflicts / tx
0.76
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #102,305,957 · 29 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
7w08w110w011w112w213w014w315w016w117w218w125w226w427w528w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1e6a248d…87d3
0xd32edf…ff58
9 touches
10 conflicts
0x95523e2a…4c01
0x065c9d…c394
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x00000000…0002
0xf5b5f7…6d70
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0019
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0029
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 0x1e6a248dac…fc87d3
Audit this contract →
← previous block·next block →recent activity