← previous blocknext block →recent activity
Analyzing
Block #85,104,755
20 transactions · 17 stateful · 2026-07-02 11:39:20 UTC
Parallelism
70/100
Blocked
41%
Avg conflicts / tx
1.1
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #85,104,755 · 20 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
2w03w14w25w38w412w013w117w018w419w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
12 touches
15 conflicts
0xfaef08b1…0696
0x34b655…2a6f
10 touches
10 conflicts
0x307414a5…7214
0x34b655…2a6f
8 touches
6 conflicts
0x922c7ebd…6600
0xc8689a…ee79
8 touches
6 conflicts
0x0806ab7b…d323
0x34b655…2a6f
8 touches
6 conflicts
0xc1647db7…f853
0x34b655…2a6f
8 touches
6 conflicts
0xc83310b1…c778
0x34b655…2a6f
8 touches
6 conflicts
0xeec29f25…1844
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
15 conflicts on slot 0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block·next block →recent activity