← previous blocknext block →recent activity
Analyzing
Block #85,804,053
27 transactions · 24 stateful · 2026-07-05 17:18:20 UTC
Parallelism
81/100
Blocked
38%
Avg conflicts / tx
0.59
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #85,804,053 · 27 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
1w02w03w08w112w113w214w015w117w118w022w123w224w326w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x033cf007…136d
0x34b655…2a6f
6 touches
3 conflicts
0x0d622e34…0000
0x681e90…ae09
6 touches
3 conflicts
0x1c5968c7…708a
0x34b655…2a6f
4 touches
1 conflict
0x7d68b808…c6e3
0x34b655…2a6f
4 touches
1 conflict
0x7e78d948…802e
0x34b655…2a6f
4 touches
1 conflict
0x9e719c7a…df63
0x34b655…2a6f
4 touches
1 conflict
0xcbd23469…a4df
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
10 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity