← previous blocknext block →recent activity
Analyzing
Block #85,180,266
13 transactions · 12 stateful · 2026-07-02 20:03:02 UTC
Parallelism
77/100
Blocked
17%
Avg conflicts / tx
0.23
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #85,180,266 · 13 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w07w011w112w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xac6f24e7…c98b
0x34b655…2a6f
4 touches
1 conflict
0xc2207d3d…59ce
0x34b655…2a6f
4 touches
1 conflict
0xc640f46e…a538
0x34b655…2a6f
4 touches
1 conflict
0xd63e616b…a07d
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x026d07f8…07a0
0x34b655…2a6f
4 touches
1 conflict
0x32317ed6…85b0
0x34b655…2a6f
4 touches
1 conflict
0x680fdd59…e84d
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
1 conflict on slot 0xac6f24e767…bec98b
Audit this contract →
← previous block·next block →recent activity