← previous blocknext block →recent activity
Analyzing
Block #86,301,743
41 transactions · 34 stateful · 2026-07-08 00:38:58 UTC
Parallelism
81/100
Blocked
53%
Avg conflicts / tx
1.15
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #86,301,743 · 41 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w010w111w012w413w117w525w628w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x44454e7d…f9fb
0xd32edf…ff58
15 touches
28 conflicts
0xcc8faac2…c766
0x065c9d…c394
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…0002
0x04fdea…47d7
6 touches
3 conflicts
0x65903ef9…2567
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0018
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0028
0x1b6862…e19c
4 touches
1 conflict
0xada193dc…5c79
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
28 conflicts on slot 0x44454e7d3e…50f9fb
Audit this contract →
← previous block·next block →recent activity