pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#85,805,649
← previous block
next block →
recent activity
Analyzing
Block #85,805,649
10 transactions · 10 stateful · 2026-07-05 17:28:59 UTC
Parallelism
80
/100
Blocked
10
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,805,649
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
updateDataFeedsValuesPartial
#3
0x0f6795d9
#4
0x0f6795d9
· blocks 1
#5
0x3f5c179b
#7
0x6a4a94d2
#8
0x445e1eb7
#9
setData
#6
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x09500602…94ea
0x34b655…2a6f
4 touches
1 conflict
0x09500602…94e9
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x39cc2185…cacb
0x34b655…2a6f
2 touches
0 conflicts
0x8e2ae9c0…6542
0x34b655…2a6f
2 touches
0 conflicts
0xc5ed5f80…43d0
0x34b655…2a6f
2 touches
0 conflicts
0xcd627ba4…e652
0x34b655…2a6f
2 touches
0 conflicts
0x01a89030…f786
0x368ee5…7ca4
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
0x0950060282…6794ea
Audit this contract →
← previous block
·
next block →
recent activity