← previous blocknext block →recent activity
Analyzing
Block #85,853,490
13 transactions · 12 stateful · 2026-07-05 22:47:41 UTC
Parallelism
54/100
Blocked
50%
Avg conflicts / tx
0.54
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #85,853,490 · 13 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w16w27w38w412w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xafd867b7…2b2d
0x34b655…2a6f
6 touches
3 conflicts
0xafd867b7…2b2e
0x34b655…2a6f
6 touches
3 conflicts
0xf3a8049c…95a6
0x34b655…2a6f
4 touches
1 conflict
0x4a90f6e1…695a
0x34b655…2a6f
4 touches
1 conflict
0x503d17fc…e0a9
0x34b655…2a6f
4 touches
1 conflict
0x5fad6fee…7714
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
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
3 conflicts on slot 0xafd867b7ed…d92b2d
Audit this contract →
← previous block·next block →recent activity