pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#97,819,508
← previous block
next block →
recent activity
Analyzing
Block #97,819,508
13 transactions · 10 stateful · 2026-08-21 04:56:50 UTC
Parallelism
85
/100
Blocked
20
%
Avg conflicts / tx
0.15
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#97,819,508
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execute
#2
transfer
#3
execPerpOps
#4
execPerpOps
#5
execPerpOps
#6
0x5acec890
· blocks 2
#9
setData
#10
0x59558d29
#11
execOrders
#12
execOrders
#7
0x5acec890
#8
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
7
w1
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7316dc00…c16a
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x08ff2573…8168
0x34b655…2a6f
2 touches
0 conflicts
0x0c478a49…ed73
0x34b655…2a6f
2 touches
0 conflicts
0x2c2761c0…476e
0x34b655…2a6f
2 touches
0 conflicts
0x49c1b8a5…98b4
0x34b655…2a6f
2 touches
0 conflicts
0x4a1e4031…b058
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
0x7316dc00d3…b5c16a
Audit this contract →
← previous block
·
next block →
recent activity