pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#85,763,203
← previous block
next block →
recent activity
Analyzing
Block #85,763,203
10 transactions · 9 stateful · 2026-07-05 12:46:11 UTC
Parallelism
60
/100
Blocked
33
%
Avg conflicts / tx
0.3
Longest chain
4
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,763,203
· 10 txs across 4 waves · depth 4
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
0x785f5745
#3
execFwdPositionOps
· blocks 1
#4
0x3f5c179b
#5
0x3f5c179b
#7
setData
#6
execFwdPositionOps
· blocks 1
#8
execOrders
· blocks 1
#9
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
6
w1
8
w2
9
w3
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa62791bc…c2ec
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xc978dec7…e3d6
0x34b655…2a6f
4 touches
1 conflict
0xda2ee2e7…968a
0x34b655…2a6f
4 touches
1 conflict
0xed82c04f…a141
0x34b655…2a6f
4 touches
1 conflict
0x1d720942…075a
0x34b655…2a6f
4 touches
1 conflict
0x3d23b41b…56ce
0x34b655…2a6f
4 touches
1 conflict
0x9a3068dd…18f0
0x34b655…2a6f
4 touches
1 conflict
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
0xa62791bced…44c2ec
Audit this contract →
← previous block
·
next block →
recent activity