← previous blocknext block →recent activity
Analyzing
Block #85,129,403
21 transactions · 19 stateful · 2026-07-02 14:24:10 UTC
Parallelism
86/100
Blocked
21%
Avg conflicts / tx
0.29
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #85,129,403 · 21 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w27w08w19w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
6 touches
3 conflicts
0xaeba93e1…a229
0xd32edf…ff58
5 touches
3 conflicts
0x3433711d…412d
0x34b655…2a6f
4 touches
1 conflict
0x25de453d…9573
0x34b655…2a6f
4 touches
1 conflict
0x3ea25e92…a36d
0x34b655…2a6f
4 touches
1 conflict
0x6167486f…db40
0x34b655…2a6f
4 touches
1 conflict
0x656bd53e…af4e
0x34b655…2a6f
4 touches
1 conflict
0xa178e1b0…b64e
0x34b655…2a6f
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: Perpl
3 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity