pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#97,709,540
← previous block
next block →
recent activity
Analyzing
Block #97,709,540
9 transactions · 9 stateful · 2026-08-20 19:41:33 UTC
Parallelism
78
/100
Blocked
11
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#97,709,540
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
transfer
#2
execOrders
· blocks 1
#4
execFwdPositionOpsV2
#5
execOrders
#6
setData
#7
0x59558d29
#8
execOrders
#3
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfc24540b…6463
0x34b655…2a6f
4 touches
1 conflict
0x36f8d65b…7aed
0x34b655…2a6f
4 touches
1 conflict
0x68c23664…74c4
0x34b655…2a6f
4 touches
1 conflict
0x0b628201…cd3c
0x34b655…2a6f
2 touches
0 conflicts
0x20492d53…80f9
0x34b655…2a6f
2 touches
0 conflicts
0xf504c9e0…be9c
0x34b655…2a6f
2 touches
0 conflicts
0x4b316516…ce0a
0x34b655…2a6f
2 touches
0 conflicts
0x5281d93a…91d8
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
0xfc24540b5d…4d6463
Audit this contract →
← previous block
·
next block →
recent activity