pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#86,126,071
← previous block
next block →
recent activity
Analyzing
Block #86,126,071
10 transactions · 8 stateful · 2026-07-07 05:06:05 UTC
Parallelism
80
/100
Blocked
25
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,126,071
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0d484c28
#2
execOrders
· blocks 1
#4
updateDataFeedsValuesPartial
#5
execFwdPositionOps
· blocks 1
#6
updatePriceFeedsIfNecessary
#8
setData
#9
execOrders
#3
execOrders
#7
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
5
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x172b0de5…980b
0x34b655…2a6f
4 touches
1 conflict
0x09500602…94e9
0x34b655…2a6f
4 touches
1 conflict
0x09500602…94ea
0x34b655…2a6f
4 touches
1 conflict
0x301e1c77…9e30
0x34b655…2a6f
2 touches
0 conflicts
0x3ab3266e…0f8f
0x34b655…2a6f
2 touches
0 conflicts
0x65392f8c…7fd2
0x34b655…2a6f
2 touches
0 conflicts
0x84a0dfbe…39f8
0x34b655…2a6f
2 touches
0 conflicts
0x85a88798…f85e
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
0x172b0de5b2…14980b
Audit this contract →
← previous block
·
next block →
recent activity