pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#98,538,471
← previous block
next block →
recent activity
Analyzing
Block #98,538,471
14 transactions · 11 stateful · 2026-08-23 17:35:46 UTC
Parallelism
86
/100
Blocked
9
%
Avg conflicts / tx
0.07
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#98,538,471
· 14 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
setData
#2
0xb264ae19
#3
updatePrices
#4
updatePrices
#5
execOrders
#6
0x59558d29
#7
0xe3a3c9cc
#8
0xaf47a8bb
#9
execFwdPositionOpsV2
#10
0xed82b078
#11
execFwdPositionOpsV2
#12
execOrders
· blocks 1
#13
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
12
w0
13
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x09106a95…1467
0x33176b…e078
2 touches
0 conflicts
0x0b0611f7…e63a
0x34b655…2a6f
2 touches
0 conflicts
0x22066be1…df9c
0x34b655…2a6f
2 touches
0 conflicts
0x3aa933e6…a6ec
0x34b655…2a6f
2 touches
0 conflicts
0x5791dd54…0d85
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
0xd98b3c102b…ca67b8
Audit this contract →
← previous block
·
next block →
recent activity