← previous blocknext block →recent activity
Analyzing
Block #85,508,399
13 transactions · 10 stateful · 2026-07-04 08:28:18 UTC
Parallelism
69/100
Blocked
30%
Avg conflicts / tx
0.23
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #85,508,399 · 13 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w212w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x23253ea8…e0a4
0x34b655…2a6f
4 touches
1 conflict
0x830b63a6…8105
0x34b655…2a6f
4 touches
1 conflict
0xfaef08b1…0696
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0002
0x04fdea…47d7
2 touches
0 conflicts
0x0934ec4c…50c8
0x34b655…2a6f
2 touches
0 conflicts
0x2907ed4d…acbf
0x34b655…2a6f
2 touches
0 conflicts
0x326f2a00…a2a6
0x34b655…2a6f
2 touches
0 conflicts
0x6c533b68…15e7
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 0x23253ea8be…0fe0a4
Audit this contract →
← previous block·next block →recent activity