pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,544,140
← previous block
next block →
recent activity
Analyzing
Block #96,544,140
8 transactions · 7 stateful · 2026-08-16 17:01:54 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,544,140
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xa96df62f
#2
0x5acec890
#3
execFwdPositionOpsV2
· blocks 1
#5
execFwdPositionOpsV2
#6
updateDataFeedsValuesPartial
#7
setData
#4
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf4c9a0df…dcd5
0x34b655…2a6f
4 touches
1 conflict
0xf4c9a0df…dcd4
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x1991d3e1…7fe0
0x34b655…2a6f
2 touches
0 conflicts
0x1cd184eb…d491
0x34b655…2a6f
2 touches
0 conflicts
0x2ac796c1…5bbc
0x34b655…2a6f
2 touches
0 conflicts
0x6272dae4…dd39
0x34b655…2a6f
2 touches
0 conflicts
0x74fd0a9b…3aaa
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
0xf4c9a0dfc5…fcdcd5
Audit this contract →
← previous block
·
next block →
recent activity