← previous blocknext block →recent activity
Analyzing
Block #85,791,698
22 transactions · 18 stateful · 2026-07-05 15:55:57 UTC
Parallelism
77/100
Blocked
50%
Avg conflicts / tx
0.64
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #85,791,698 · 22 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w27w08w110w011w112w018w119w220w321w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc7f7d98f…cfe7
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xca2926e0…61b5
0x34b655…2a6f
6 touches
3 conflicts
0x56a919c4…ab49
0xee8c0e…1242
6 touches
3 conflicts
0x64c57c87…5e42
0x34b655…2a6f
5 touches
3 conflicts
0x172b0de5…980b
0x34b655…2a6f
4 touches
1 conflict
0x3238e64a…5035
0x34b655…2a6f
4 touches
1 conflict
0x38d0f220…01f4
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 0xc7f7d98fdd…77cfe7
Audit this contract →
← previous block·next block →recent activity