pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#97,682,801
← previous block
next block →
recent activity
Analyzing
Block #97,682,801
10 transactions · 10 stateful · 2026-08-20 17:25:36 UTC
Parallelism
80
/100
Blocked
30
%
Avg conflicts / tx
0.3
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#97,682,801
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#2
execOrders
· blocks 1
#3
updateDataFeedsValuesPartial
#4
execFwdPositionOpsV2
· blocks 1
#7
setData
#8
0x59558d29
#5
execFwdPositionOpsV2
#6
execFwdPositionOpsV2
#9
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w0
4
w0
5
w1
6
w1
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2ed00f98…da9f
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xe41626f9…dd93
0x34b655…2a6f
4 touches
1 conflict
0xb7b446d2…2006
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…001c
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…002c
0x1b6862…e19c
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
0x2ed00f9866…11da9f
Audit this contract →
← previous block
·
next block →
recent activity