pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#86,989,870
← previous block
next block →
recent activity
Analyzing
Block #86,989,870
12 transactions · 12 stateful · 2026-07-11 05:19:56 UTC
Parallelism
83
/100
Blocked
8
%
Avg conflicts / tx
0.17
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,989,870
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
execFwdPositionOps
· blocks 1
#3
execFwdPositionOps
· blocks 1
#4
updateDataFeedsValuesPartial
#6
0x3f5c179b
#7
0x57368ddf
#8
0x6a51d2f3
#9
setData
#10
0x785f5745
#11
execOrders
#5
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x06eb454c…0ef9
0x34b655…2a6f
4 touches
1 conflict
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0x45c033be…0aad
0x34b655…2a6f
4 touches
1 conflict
0x619c81de…01b4
0x34b655…2a6f
4 touches
1 conflict
0x64852187…6caf
0x34b655…2a6f
4 touches
1 conflict
0x64852187…6cb0
0x34b655…2a6f
4 touches
1 conflict
0x65e6e603…cb44
0x34b655…2a6f
4 touches
1 conflict
0x65e6e603…cb45
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
0x06eb454c26…550ef9
Audit this contract →
← previous block
·
next block →
recent activity