pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#86,490,537
← previous block
next block →
recent activity
Analyzing
Block #86,490,537
11 transactions · 7 stateful · 2026-07-08 21:40:39 UTC
Parallelism
82
/100
Blocked
14
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,490,537
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrders
· blocks 1
#2
0x5a5d9a99
#3
updateDataFeedsValuesPartial
#5
execFwdPositionOps
#6
setData
#7
0xae66a0…5519
#8
0x83e6be…a72f
#9
execOrders
#10
0x5d2fd812
#4
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8bf661cb…bcd2
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x1d3b8ae2…d6f0
0x34b655…2a6f
2 touches
0 conflicts
0x3b6e959d…158f
0x34b655…2a6f
2 touches
0 conflicts
0x469dac8d…3411
0x34b655…2a6f
2 touches
0 conflicts
0x548145a9…cfce
0x34b655…2a6f
2 touches
0 conflicts
0x63c900f4…2600
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
0x8bf661cb38…d4bcd2
Audit this contract →
← previous block
·
next block →
recent activity