pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#85,766,204
← previous block
next block →
recent activity
Analyzing
Block #85,766,204
8 transactions · 5 stateful · 2026-07-05 13:06:11 UTC
Parallelism
75
/100
Blocked
20
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,766,204
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0f6795d9
· blocks 1
#2
updateDataFeedsValuesPartial
#3
updateDataFeedsValuesPartial
#5
setData
#6
0x2f2274…90a3
#7
0x448af5…3dc4
#4
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4c6b0b95…7758
0x34b655…2a6f
4 touches
1 conflict
0x0ab54c30…b88e
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x10797f0b…439a
0x34b655…2a6f
2 touches
0 conflicts
0x109d8a52…a7b7
0x34b655…2a6f
2 touches
0 conflicts
0x134b2009…e129
0x34b655…2a6f
2 touches
0 conflicts
0x247efa85…c7b4
0x34b655…2a6f
2 touches
0 conflicts
0x2d071de0…c86e
0x34b655…2a6f
2 touches
0 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
1 conflict on slot
0x4c6b0b95e7…ff7758
Audit this contract →
← previous block
·
next block →
recent activity