← previous blocknext block →recent activity
Analyzing
Block #83,640,783
35 transactions · 27 stateful · 2026-06-25 16:58:23 UTC
Parallelism
83/100
Blocked
52%
Avg conflicts / tx
0.8
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #83,640,783 · 35 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
1w02w13w24w35w46w07w18w09w110w215w319w321w523w025w128w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x04eec56d…8e7a
0xd32edf…ff58
11 touches
15 conflicts
0x00000000…0002
0xaa7ee7…f0e4
8 touches
6 conflicts
0x485d2778…aa5d
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001b
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002b
0x1b6862…e19c
4 touches
1 conflict
0x00000000…003d
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
15 conflicts on slot 0x04eec56de3…ea8e7a
Audit this contract →
← previous block·next block →recent activity