← previous blocknext block →recent activity
Analyzing
Block #86,305,700
30 transactions · 26 stateful · 2026-07-08 01:05:24 UTC
Parallelism
67/100
Blocked
54%
Avg conflicts / tx
1.53
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #86,305,700 · 30 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w68w710w820w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xefd166a4…8173
0xd32edf…ff58
17 touches
36 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0xcc8faac2…c766
0x065c9d…c394
4 touches
1 conflict
0x46cb45de…a566
0x188d58…ea8e
4 touches
1 conflict
0x46cb45de…a567
0x188d58…ea8e
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0013
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
36 conflicts on slot 0xefd166a4e0…a08173
Audit this contract →
← previous block·next block →recent activity