← previous blocknext block →recent activity
Analyzing
Block #85,161,058
20 transactions · 18 stateful · 2026-07-02 17:55:08 UTC
Parallelism
75/100
Blocked
44%
Avg conflicts / tx
0.85
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #85,161,058 · 20 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
2w04w15w26w37w08w19w210w311w418w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7b0bca9e…63b6
0x34b655…2a6f
10 touches
10 conflicts
0xea2644f5…8c97
0x34b655…2a6f
10 touches
10 conflicts
0x97fe3267…5e87
0x34b655…2a6f
10 touches
10 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
10 touches
10 conflicts
0x63b15849…80b2
0x34b655…2a6f
8 touches
6 conflicts
0x8b205e73…37b4
0x34b655…2a6f
8 touches
6 conflicts
0xa1571d54…ae41
0x34b655…2a6f
8 touches
6 conflicts
0xabbbfd15…1af3
0x34b655…2a6f
8 touches
6 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
10 conflicts on slot 0x7b0bca9e38…f963b6
Audit this contract →
← previous block·next block →recent activity