← previous blocknext block →recent activity
Analyzing
Block #86,300,858
27 transactions · 22 stateful · 2026-07-08 00:33:01 UTC
Parallelism
81/100
Blocked
59%
Avg conflicts / tx
0.78
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,300,858 · 27 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
1w02w13w24w36w09w110w011w112w213w014w116w417w018w220w221w424w125w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcbb8ab99…ffc1
0xd32edf…ff58
9 touches
10 conflicts
0x00000000…0002
0x04fdea…47d7
6 touches
3 conflicts
0x7016875b…2be6
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
0x00000000…0028
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 0xcbb8ab99f8…08ffc1
Audit this contract →
← previous block·next block →recent activity