pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,508,380
← previous block
next block →
recent activity
Analyzing
Block #96,508,380
8 transactions · 6 stateful · 2026-08-16 14:02:03 UTC
Parallelism
75
/100
Blocked
33
%
Avg conflicts / tx
0.25
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,508,380
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5acec890
· blocks 2
#3
execFwdPositionOpsV2
#5
execFwdPositionOpsV2
#6
updateDataFeedsValuesPartial
#7
setData
#2
0x5acec890
#4
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xea1b8c07…b969
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x0fc81850…e472
0x34b655…2a6f
2 touches
0 conflicts
0x19439a65…eb51
0x34b655…2a6f
2 touches
0 conflicts
0x28e5dbea…2f7f
0x34b655…2a6f
2 touches
0 conflicts
0x2acdf73b…fbae
0x34b655…2a6f
2 touches
0 conflicts
0x2ad2e6d1…e192
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
0xea1b8c07ee…d0b969
Audit this contract →
← previous block
·
next block →
recent activity