pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#86,540,601
← previous block
next block →
recent activity
Analyzing
Block #86,540,601
9 transactions · 8 stateful · 2026-07-09 03:14:57 UTC
Parallelism
78
/100
Blocked
13
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,540,601
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xb5ce855a
#2
updateDataFeedsValuesPartial
#3
updateDataFeedsValuesPartial
#4
updateDataFeedsValuesPartial
#5
0x5a5d9a99
#6
setData
#7
0x0f6795d9
· blocks 1
#8
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
7
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4e58f1d6…2fca
0x34b655…2a6f
4 touches
1 conflict
0x12f25643…f001
0x34b655…2a6f
4 touches
1 conflict
0x31d88d27…7617
0x34b655…2a6f
4 touches
1 conflict
0x091fa1da…11fe
0x0a4fcb…a602
2 touches
0 conflicts
0x2fe25dd8…48df
0x0a4fcb…a602
2 touches
0 conflicts
0x6719f13a…ca11
0x0a4fcb…a602
2 touches
0 conflicts
0x6bd9b2de…7d72
0x0f2610…0edc
2 touches
0 conflicts
0x09106a95…1467
0x33176b…e078
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
0x4e58f1d685…d82fca
Audit this contract →
← previous block
·
next block →
recent activity