pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,653,044
← previous block
next block →
recent activity
Analyzing
Block #96,653,044
13 transactions · 10 stateful · 2026-08-17 02:09:39 UTC
Parallelism
85
/100
Blocked
10
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,653,044
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrder
#2
execOrder
· blocks 1
#3
execFwdPositionOpsV2
#4
execFwdPositionOpsV2
#5
0x3f5c179b
#6
0x3f5c179b
#7
forward
#8
updateDataFeedsValuesPartial
#9
updateDataFeedsValuesPartial
#10
updateDataFeedsValuesPartial
#11
setData
#12
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
12
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x745952b2…d90c
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…00c9
0x34b655…2a6f
2 touches
0 conflicts
0x0e3b59e9…d9d0
0x34b655…2a6f
2 touches
0 conflicts
0x1321736a…43e3
0x34b655…2a6f
2 touches
0 conflicts
0x3cb8c8c3…22f4
0x34b655…2a6f
2 touches
0 conflicts
0x42522e76…2592
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
0x745952b2a0…a6d90c
Audit this contract →
← previous block
·
next block →
recent activity