← previous blocknext block →recent activity
Analyzing
Block #85,253,110
10 transactions · 9 stateful · 2026-07-03 04:08:19 UTC
Parallelism
80/100
Blocked
11%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,253,110 · 10 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x57a080db…7fde
0x34b655…2a6f
4 touches
1 conflict
0x6b7e2ade…d95b
0x34b655…2a6f
4 touches
1 conflict
0x00c45c58…7df2
0x34b655…2a6f
2 touches
0 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
2 touches
0 conflicts
0x79e1370e…9c68
0x34b655…2a6f
2 touches
0 conflicts
0x801058a8…5bc3
0x34b655…2a6f
2 touches
0 conflicts
0xb3af583a…b098
0x34b655…2a6f
2 touches
0 conflicts
0xc0b9bd73…7f1c
0x34b655…2a6f
2 touches
0 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: Perpl
1 conflict on slot 0x57a080db21…097fde
Audit this contract →
← previous block·next block →recent activity