← previous blocknext block →recent activity
Analyzing
Block #87,066,231
24 transactions · 22 stateful · 2026-07-11 13:50:05 UTC
Parallelism
79/100
Blocked
41%
Avg conflicts / tx
0.63
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,066,231 · 24 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
1w02w13w24w313w014w115w416w117w218w219w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x795fe2d5…e0c3
0xd32edf…ff58
9 touches
10 conflicts
0x3d6fd7d2…b868
0x065c9d…c394
4 touches
1 conflict
0x52e69143…95ad
0x065c9d…c394
4 touches
1 conflict
0xd35bb5ac…3586
0x065c9d…c394
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0018
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 0x795fe2d5bf…83e0c3
Audit this contract →
← previous block·next block →recent activity