pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#85,938,708
← previous block
next block →
recent activity
Analyzing
Block #85,938,708
10 transactions · 7 stateful · 2026-07-06 08:15:20 UTC
Parallelism
80
/100
Blocked
14
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,938,708
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrder
· blocks 1
#3
execFwdPositionOps
#4
0x3f5c179b
#5
execFwdPositionOps
#6
updateDataFeedsValuesPartial
#7
setData
#8
0xa23389…dc85
#9
0x38ed87…443d
#2
execOrder
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xec7d120d…7084
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x03da8cec…05df
0x34b655…2a6f
2 touches
0 conflicts
0x1544d128…23e7
0x34b655…2a6f
2 touches
0 conflicts
0x2b5101ac…090b
0x34b655…2a6f
2 touches
0 conflicts
0x394971b4…63d9
0x34b655…2a6f
2 touches
0 conflicts
0x588e3422…2c08
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
0xec7d120df9…5d7084
Audit this contract →
← previous block
·
next block →
recent activity