← previous blocknext block →recent activity
Analyzing
Block #91,439,024
25 transactions · 18 stateful · 2026-07-29 20:28:51 UTC
Parallelism
80/100
Blocked
44%
Avg conflicts / tx
0.6
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #91,439,024 · 25 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
1w02w16w28w312w014w415w118w120w021w122w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd9b0cde7…5758
0xd32edf…ff58
9 touches
10 conflicts
0xc61d8a1d…18fd
0x34b655…2a6f
6 touches
3 conflicts
0x4f3a6b4a…3819
0x34b655…2a6f
6 touches
3 conflicts
0x11435133…4bf8
0x34b655…2a6f
6 touches
3 conflicts
0x388114fc…db6c
0x34b655…2a6f
4 touches
1 conflict
0x388114fc…db6d
0x34b655…2a6f
4 touches
1 conflict
0xf3d10975…0d07
0x34b655…2a6f
4 touches
1 conflict
0x85a88798…f85e
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
10 conflicts on slot 0xd9b0cde701…525758
Audit this contract →
← previous block·next block →recent activity