pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#98,425,216
← previous block
next block →
recent activity
Analyzing
Block #98,425,216
12 transactions · 10 stateful · 2026-08-23 07:58:18 UTC
Parallelism
83
/100
Blocked
10
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#98,425,216
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
matchOrders
#2
0x59558d29
#3
execPerpOps
#4
execPerpOps
#5
0x5acec890
· blocks 1
#6
0x3f5c179b
#7
execFwdPositionOpsV2
#8
execFwdPositionOpsV2
#9
proposeResolution
#10
setData
#11
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
11
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x676f9f01…a8ac
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x22e0cc1d…ad04
0x34b655…2a6f
2 touches
0 conflicts
0x366a19b0…f065
0x34b655…2a6f
2 touches
0 conflicts
0x45885570…ed97
0x34b655…2a6f
2 touches
0 conflicts
0x65364b5d…2773
0x34b655…2a6f
2 touches
0 conflicts
0x65bd465d…9770
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
0x676f9f01ee…dea8ac
Audit this contract →
← previous block
·
next block →
recent activity