← previous blocknext block →recent activity
Analyzing
Block #85,160,591
18 transactions · 17 stateful · 2026-07-02 17:52:03 UTC
Parallelism
83/100
Blocked
24%
Avg conflicts / tx
0.28
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #85,160,591 · 18 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
3w05w16w216w117w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x40b5f387…a164
0x34b655…2a6f
6 touches
3 conflicts
0xb44d5376…33cc
0x34b655…2a6f
6 touches
3 conflicts
0xe72b543d…f824
0x34b655…2a6f
6 touches
3 conflicts
0x339fca69…8fd8
0x34b655…2a6f
4 touches
1 conflict
0x4b93c963…e48b
0x34b655…2a6f
4 touches
1 conflict
0x548145a9…cfce
0x34b655…2a6f
4 touches
1 conflict
0x63b15849…80b2
0x34b655…2a6f
4 touches
1 conflict
0x742072b0…1af8
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 0x40b5f38715…7ba164
Audit this contract →
← previous block·next block →recent activity