← previous blocknext block →recent activity
Analyzing
Block #85,162,668
15 transactions · 13 stateful · 2026-07-02 18:05:51 UTC
Parallelism
73/100
Blocked
38%
Avg conflicts / tx
0.53
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #85,162,668 · 15 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
1w04w16w17w29w313w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7fffd49d…772a
0x34b655…2a6f
8 touches
6 conflicts
0x5efea426…3d66
0x34b655…2a6f
6 touches
3 conflicts
0x7b7a78ce…a432
0x34b655…2a6f
4 touches
1 conflict
0xdeddb1c8…0d40
0x34b655…2a6f
4 touches
1 conflict
0xe1835e8b…1a99
0x34b655…2a6f
4 touches
1 conflict
0x026d07f8…07a0
0x34b655…2a6f
4 touches
1 conflict
0xfd2c2d84…ef69
0x34b655…2a6f
4 touches
1 conflict
0x0ec96631…b0f1
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
6 conflicts on slot 0x7fffd49db6…f8772a
Audit this contract →
← previous block·next block →recent activity