← previous blocknext block →recent activity
Analyzing
Block #91,209,731
37 transactions · 33 stateful · 2026-07-29 01:13:01 UTC
Parallelism
89/100
Blocked
27%
Avg conflicts / tx
0.35
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #91,209,731 · 37 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
1w03w14w25w110w312w025w127w230w031w132w033w134w035w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5af14639…4f97
0xd32edf…ff58
7 touches
6 conflicts
0x09106a95…1467
0x33176b…e078
4 touches
1 conflict
0x5d1ac445…5233
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
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
6 conflicts on slot 0x5af146391c…124f97
Audit this contract →
← previous block·next block →recent activity