pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,713,762
← previous block
next block →
recent activity
Analyzing
Block #95,713,762
10 transactions · 9 stateful · 2026-08-13 19:24:28 UTC
Parallelism
80
/100
Blocked
11
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,713,762
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
updateDataFeedsValuesPartial
#3
updatePosition
#4
execFwdPositionOpsV2
#5
execFwdPositionOpsV2
· blocks 1
#7
0x6a7e1a64
#8
0xd708c5d8
#9
setData
#6
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd4305f3b…7f3e
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0xa27fa22d…7dca
0x54cd53…9e7d
2 touches
0 conflicts
0x10ce7494…f7e4
0x6657d1…8ccc
2 touches
0 conflicts
0x2ab9a215…fcc2
0x6657d1…8ccc
2 touches
0 conflicts
0x2b83f59e…652a
0x6657d1…8ccc
2 touches
0 conflicts
0x30952af0…a19b
0x6657d1…8ccc
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
0xd4305f3b6e…5c7f3e
Audit this contract →
← previous block
·
next block →
recent activity