pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#98,573,688
← previous block
next block →
recent activity
Analyzing
Block #98,573,688
12 transactions · 10 stateful · 2026-08-23 20:39:45 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,573,688
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
0x6bb618…ac10
#3
0xd10474…651b
#4
0x59558d29
#5
execPerpOps
#6
forward
#7
setData
#8
execFwdPositionOpsV2
· blocks 1
#10
transfer
#11
0x6a8b5b08
#9
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
8
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…00c9
0x34b655…2a6f
4 touches
1 conflict
0xd6113c0f…0a4b
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xbf3b12e0…35d9
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…641f
0x34b655…2a6f
4 touches
1 conflict
0xd4305f3b…7f3d
0x34b655…2a6f
4 touches
1 conflict
0xa7b52ff9…8d5b
0x34b655…2a6f
3 touches
1 conflict
0xb2a6de34…9119
0x34b655…2a6f
3 touches
1 conflict
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
0x0000000000…0000c9
Audit this contract →
← previous block
·
next block →
recent activity