pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,142,604
← previous block
next block →
recent activity
Analyzing
Block #96,142,604
8 transactions · 7 stateful · 2026-08-15 07:22:04 UTC
Parallelism
75
/100
Blocked
14
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,142,604
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
execFwdPositionOpsV2
· blocks 1
#3
execFwdPositionOpsV2
#4
executeBatch
#5
0x9e76c652
#7
setData
#6
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7c09c53e…64b4
0x34b655…2a6f
4 touches
1 conflict
0x9ca6fa7b…aeb3
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x0087ca84…0b18
0x34b655…2a6f
2 touches
0 conflicts
0x04994ed2…9032
0x34b655…2a6f
2 touches
0 conflicts
0x08711da7…1591
0x34b655…2a6f
2 touches
0 conflicts
0x155e52ca…fac7
0x34b655…2a6f
2 touches
0 conflicts
0x1565183a…e0a0
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
0x7c09c53e5b…3864b4
Audit this contract →
← previous block
·
next block →
recent activity