← previous blocknext block →recent activity
Analyzing
Block #95,022,184
25 transactions · 19 stateful · 2026-08-11 09:10:35 UTC
Parallelism
84/100
Blocked
47%
Avg conflicts / tx
0.6
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #95,022,184 · 25 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
2w03w05w16w07w18w19w212w213w214w018w319w324w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x658d09ab…562b
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…0002
0xeae24c…0be0
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xb33ff823…1188
0x065c9d…c394
4 touches
1 conflict
0x11258774…9892
0x2a68ba…90c5
4 touches
1 conflict
0x2b5101ac…090b
0x34b655…2a6f
4 touches
1 conflict
0x3439dfbc…0d03
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
6 conflicts on slot 0x658d09ab9f…fd562b
Audit this contract →
← previous block·next block →recent activity