← previous blocknext block →recent activity
Analyzing
Block #85,509,587
13 transactions · 9 stateful · 2026-07-04 08:36:13 UTC
Parallelism
85/100
Blocked
11%
Avg conflicts / tx
0.15
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,509,587 · 13 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
1w05w011w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x50887223…db7f
0x34b655…2a6f
4 touches
1 conflict
0x0ab54c30…b88e
0x34b655…2a6f
4 touches
1 conflict
0x23253ea8…e0a4
0x34b655…2a6f
4 touches
1 conflict
0xcdc1731c…b91a
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0x29ba8cb6…dcee
0x34b655…2a6f
2 touches
0 conflicts
0x30faf03c…78b1
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 0x508872232f…04db7f
Audit this contract →
← previous block·next block →recent activity