← previous blocknext block →recent activity
Analyzing
Block #85,132,612
20 transactions · 19 stateful · 2026-07-02 14:45:38 UTC
Parallelism
50/100
Blocked
53%
Avg conflicts / tx
2.55
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #85,132,612 · 20 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w25w36w47w58w615w616w717w818w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x366f651e…6100
0x34b655…2a6f
16 touches
28 conflicts
0xfaef08b1…0696
0x34b655…2a6f
14 touches
21 conflicts
0x97c67486…27fe
0x34b655…2a6f
12 touches
15 conflicts
0x922c7ebd…6600
0xc8689a…ee79
12 touches
15 conflicts
0x8e5cc690…b06b
0x34b655…2a6f
12 touches
15 conflicts
0x7ae63663…9d94
0x34b655…2a6f
12 touches
15 conflicts
0xe47478a3…a058
0x34b655…2a6f
12 touches
15 conflicts
0xec0e0220…cb90
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
28 conflicts on slot 0x366f651e17…e36100
Audit this contract →
← previous block·next block →recent activity