← previous blocknext block →recent activity
Analyzing
Block #102,816,144
37 transactions · 28 stateful · 2026-09-07 17:44:20 UTC
Parallelism
84/100
Blocked
46%
Avg conflicts / tx
0.7
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #102,816,144 · 37 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
1w05w07w18w210w011w012w113w214w318w119w020w125w130w431w232w334w536w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc008cbd3…afb2
0xd32edf…ff58
9 touches
10 conflicts
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0xfcb7b8b2…ebb3
0x065c9d…c394
6 touches
3 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0x15698ac9…2a46
0x34b655…2a6f
6 touches
3 conflicts
0x443a3e47…f4a4
0x065c9d…c394
6 touches
3 conflicts
0x45f562b2…9294
0x34ae4d…3fc5
4 touches
1 conflict
0x8488f10f…9353
0x34ae4d…3fc5
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 0xc008cbd365…dbafb2
Audit this contract →
← previous block·next block →recent activity