pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#97,356,418
← previous block
next block →
recent activity
Analyzing
Block #97,356,418
12 transactions · 11 stateful · 2026-08-19 13:28:10 UTC
Parallelism
83
/100
Blocked
9
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#97,356,418
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
0xab083028
#3
execPerpOps
#4
batchUpdate
#5
execFwdPositionOpsV2
· blocks 1
#6
execFwdPositionOpsV2
#8
setData
#9
0x4cb2db39
#10
0x59558d29
#11
execOrders
#7
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe4b131c9…c602
0x34b655…2a6f
4 touches
1 conflict
0x8900cf87…5261
0x34b655…2a6f
4 touches
1 conflict
0xf18906a6…d2e3
0x34b655…2a6f
4 touches
1 conflict
0xff533a5f…685e
0x34b655…2a6f
4 touches
1 conflict
0x8c674048…d0d6
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
2 touches
0 conflicts
0x42522e76…2592
0x34b655…2a6f
2 touches
0 conflicts
0x42522e76…2593
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
0xe4b131c993…9bc602
Audit this contract →
← previous block
·
next block →
recent activity