← previous blocknext block →recent activity
Analyzing
Block #85,276,287
10 transactions · 9 stateful · 2026-07-03 06:42:37 UTC
Parallelism
80/100
Blocked
11%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,276,287 · 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
1w08w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x511ecf07…8ed0
0x34b655…2a6f
4 touches
1 conflict
0x74888025…a5b8
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x00c45c58…7df2
0x34b655…2a6f
2 touches
0 conflicts
0x03a55247…abfe
0x34b655…2a6f
2 touches
0 conflicts
0x0d5c3227…f576
0x34b655…2a6f
2 touches
0 conflicts
0x1a3c88a0…8e52
0x34b655…2a6f
2 touches
0 conflicts
0x22e0cc1d…ad0d
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 0x511ecf073e…d98ed0
Audit this contract →
← previous block·next block →recent activity