pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#89,761,097
← previous block
next block →
recent activity
Analyzing
Block #89,761,097
10 transactions · 9 stateful · 2026-07-23 23:22:41 UTC
Parallelism
80
/100
Blocked
11
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#89,761,097
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execPerpOps
#2
execPerpOps
#3
updatePrices
#4
execFwdPositionOps
· blocks 1
#6
execFwdPositionOps
#7
0x6a62a2b9
#8
setData
#9
execOrders
#5
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4aa7bc6e…96f3
0x34b655…2a6f
4 touches
1 conflict
0x5dd18eb2…4d66
0x34b655…2a6f
4 touches
1 conflict
0x38f504a9…a8bf
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0xf3343d6f…bbde
0x34b655…2a6f
4 touches
1 conflict
0xf3343d6f…bbdf
0x34b655…2a6f
4 touches
1 conflict
0x7aad02c6…b979
0x34b655…2a6f
4 touches
1 conflict
0x48083964…6bfa
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
0x4aa7bc6e2a…4e96f3
Audit this contract →
← previous block
·
next block →
recent activity