pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#85,574,709
← previous block
next block →
recent activity
Analyzing
Block #85,574,709
9 transactions · 9 stateful · 2026-07-04 15:49:51 UTC
Parallelism
78
/100
Blocked
11
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,574,709
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
updatePrices
#3
0x6a492c16
#4
0x5a5d9a99
· blocks 1
#5
updateDataFeedsValuesPartial
#6
updateDataFeedsValuesPartial
#7
setData
#8
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x31616f97…1acc
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x00000000…0002
0x04fdea…47d7
2 touches
0 conflicts
0x427c9fc4…5cee
0x34b655…2a6f
2 touches
0 conflicts
0x4826d3fe…c99e
0x34b655…2a6f
2 touches
0 conflicts
0x55807665…9c75
0x34b655…2a6f
2 touches
0 conflicts
0x6b52c26b…161e
0x34b655…2a6f
2 touches
0 conflicts
0x9b2c9ea3…e825
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
0x31616f9701…df1acc
Audit this contract →
← previous block
·
next block →
recent activity