← previous blocknext block →recent activity
Analyzing
Block #85,138,514
19 transactions · 18 stateful · 2026-07-02 15:25:00 UTC
Parallelism
68/100
Blocked
28%
Avg conflicts / tx
0.68
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #85,138,514 · 19 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
3w04w15w26w312w015w016w417w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
8 touches
6 conflicts
0xfaef08b1…0696
0x34b655…2a6f
8 touches
6 conflicts
0x132cba5e…5bf1
0x34b655…2a6f
6 touches
3 conflicts
0x1aab19aa…6852
0x34b655…2a6f
6 touches
3 conflicts
0x1fe6c207…4b3f
0x34b655…2a6f
6 touches
3 conflicts
0x4f942181…ac42
0x34b655…2a6f
6 touches
3 conflicts
0x64cdbccd…1c59
0x34b655…2a6f
6 touches
3 conflicts
0x69e7975b…6564
0x34b655…2a6f
6 touches
3 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
6 conflicts on slot 0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block·next block →recent activity