← previous blocknext block →recent activity
Analyzing
Block #85,523,858
23 transactions · 16 stateful · 2026-07-04 10:11:15 UTC
Parallelism
78/100
Blocked
38%
Avg conflicts / tx
0.43
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #85,523,858 · 23 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
1w02w13w24w37w38w420w021w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x38b5b2ce…c5bb
0xfa32f9…f3f0
8 touches
6 conflicts
0x00000000…0001
0xfa32f9…f3f0
8 touches
6 conflicts
0x00000000…0000
0xfa32f9…f3f0
8 touches
6 conflicts
0x9194f4a3…10b8
0x754704…b603
8 touches
6 conflicts
0x99f666e3…b2a2
0x3bd359…433a
8 touches
6 conflicts
0xc2aacf41…54fe
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
6 touches
3 conflicts
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: 0xfa32f9ec…fef3f0
6 conflicts on slot 0x38b5b2ceac…4cc5bb
Audit this contract →
← previous block·next block →recent activity