pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#86,305,380
← previous block
next block →
recent activity
Analyzing
Block #86,305,380
9 transactions · 8 stateful · 2026-07-08 01:03:15 UTC
Parallelism
67
/100
Blocked
25
%
Avg conflicts / tx
0.33
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,305,380
· 9 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
execOrders
· blocks 2
#3
forward
#5
updateDataFeedsValuesPartial
#6
0x6a4da24b
#7
setData
#8
execOrders
#2
execOrders
· blocks 1
#4
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
4
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xacd1b162…bee6
0x34b655…2a6f
6 touches
3 conflicts
0xd45e7a3b…85f7
0x34b655…2a6f
4 touches
1 conflict
0x9358e51b…f0ae
0x34b655…2a6f
4 touches
1 conflict
0xec0e0220…cb90
0x34b655…2a6f
4 touches
1 conflict
0xefa65ccf…1078
0x34b655…2a6f
4 touches
1 conflict
0x43e3decb…be40
0x34b655…2a6f
4 touches
1 conflict
0x89aa12d5…31ee
0x34b655…2a6f
2 touches
0 conflicts
0xb075fe10…2d4f
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
3 conflicts on slot
0xacd1b16256…3bbee6
Audit this contract →
← previous block
·
next block →
recent activity