← previous blocknext block →recent activity
Analyzing
Block #85,107,706
21 transactions · 20 stateful · 2026-07-02 11:59:02 UTC
Parallelism
67/100
Blocked
30%
Avg conflicts / tx
1.1
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #85,107,706 · 21 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w27w38w417w018w519w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5ec64628…72e4
0x34b655…2a6f
14 touches
21 conflicts
0x21f3627e…adb0
0x34b655…2a6f
10 touches
10 conflicts
0x22e0cc1d…ad06
0x34b655…2a6f
10 touches
10 conflicts
0x22e0cc1d…ad07
0x34b655…2a6f
10 touches
10 conflicts
0x922c7ebd…6600
0xc8689a…ee79
10 touches
10 conflicts
0x6286953c…1cdf
0x34b655…2a6f
10 touches
10 conflicts
0x63b15849…80b2
0x34b655…2a6f
10 touches
10 conflicts
0xcfa965cc…6fcf
0x34b655…2a6f
10 touches
10 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
21 conflicts on slot 0x5ec6462858…6272e4
Audit this contract →
← previous block·next block →recent activity