← previous blocknext block →recent activity
Analyzing
Block #85,177,973
14 transactions · 13 stateful · 2026-07-02 19:47:45 UTC
Parallelism
71/100
Blocked
23%
Avg conflicts / tx
0.64
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #85,177,973 · 14 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w15w26w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x086db8fc…0024
0x34b655…2a6f
8 touches
6 conflicts
0xfaef08b1…0696
0x34b655…2a6f
8 touches
6 conflicts
0x68953fc6…bd46
0x34b655…2a6f
8 touches
6 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
8 touches
6 conflicts
0x922c7ebd…6600
0xc8689a…ee79
6 touches
3 conflicts
0x309eb1ab…f5c8
0x34b655…2a6f
6 touches
3 conflicts
0x51a914cf…a822
0x34b655…2a6f
6 touches
3 conflicts
0x7c0bdc54…9dde
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 0x086db8fc6e…830024
Audit this contract →
← previous block·next block →recent activity