pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#87,420,004
← previous block
next block →
recent activity
Analyzing
Block #87,420,004
11 transactions · 9 stateful · 2026-07-13 05:15:59 UTC
Parallelism
82
/100
Blocked
22
%
Avg conflicts / tx
0.27
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#87,420,004
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
updatePrices
#3
execOrders
· blocks 1
#4
execPerpOps
#5
execFwdPositionOps
· blocks 2
#7
0xed82b078
#8
updateDataFeedsValuesPartial
#9
setData
#6
execFwdPositionOps
#10
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
5
w0
6
w1
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x27b1a71a…458d
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xf2112d98…bb04
0x34b655…2a6f
4 touches
1 conflict
0x00df1127…6fe4
0x34b655…2a6f
2 touches
0 conflicts
0x157dbfb2…4089
0x34b655…2a6f
2 touches
0 conflicts
0x1fab1722…aec5
0x34b655…2a6f
2 touches
0 conflicts
0x3d4584df…ffed
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
0x27b1a71a9a…dd458d
Audit this contract →
← previous block
·
next block →
recent activity