← previous blocknext block →recent activity
Analyzing
Block #86,493,799
23 transactions · 19 stateful · 2026-07-08 22:02:24 UTC
Parallelism
74/100
Blocked
53%
Avg conflicts / tx
0.87
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,493,799 · 23 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
1w02w13w24w35w16w07w08w111w413w115w416w520w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2fa39330…7da7
0xd32edf…ff58
9 touches
10 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xed660153…a905
0x34b655…2a6f
6 touches
3 conflicts
0x774daa7c…4847
0x065c9d…c394
5 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001c
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002c
0x1b6862…e19c
4 touches
1 conflict
0xa4f80979…4d71
0x065c9d…c394
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 0x2fa39330a4…347da7
Audit this contract →
← previous block·next block →recent activity