pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#86,627,244
← previous block
next block →
recent activity
Analyzing
Block #86,627,244
12 transactions · 10 stateful · 2026-07-09 12:55:40 UTC
Parallelism
83
/100
Blocked
10
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,627,244
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
updateDataFeedsValuesPartial
#3
execFwdPositionOps
· blocks 1
#4
executeBatch
#5
batchUpdate
#6
forward
#8
0x6a4f9ac4
#9
setData
#10
0x0f305f…8e86
#11
execOrders
#7
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x2130a548…c1de
0x34b655…2a6f
2 touches
0 conflicts
0x708f4f51…40e8
0x34b655…2a6f
2 touches
0 conflicts
0xc058fc55…c02c
0x34b655…2a6f
2 touches
0 conflicts
0xd92f834e…ad86
0x34b655…2a6f
2 touches
0 conflicts
0xe26c4e53…94c2
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
0x482471adbb…39122f
Audit this contract →
← previous block
·
next block →
recent activity