pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,086,254
← previous block
next block →
recent activity
Analyzing
Block #96,086,254
12 transactions · 12 stateful · 2026-08-15 02:38:36 UTC
Parallelism
83
/100
Blocked
17
%
Avg conflicts / tx
0.17
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,086,254
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrder
#2
execFwdPositionOpsV2
· blocks 1
#4
0x222d4ad6
#5
0x3f5c179b
#6
0x57368ddf
#7
execFwdPositionOpsV2
#8
updateDataFeedsValuesPartial
#9
transfer
· blocks 1
#11
setData
#3
execFwdPositionOpsV2
#10
transfer
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
9
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa4e9800f…4ab0
0x34b655…2a6f
4 touches
1 conflict
0xde08e622…d1ce
0x34b655…2a6f
4 touches
1 conflict
0x45911da6…5523
0x34b655…2a6f
4 touches
1 conflict
0x7e731aca…53ac
0x34b655…2a6f
4 touches
1 conflict
0x42041fec…bd86
0x754704…b603
4 touches
1 conflict
0x0494220d…abf7
0x34b655…2a6f
2 touches
0 conflicts
0x0dd3d3cd…7281
0x34b655…2a6f
2 touches
0 conflicts
0x1088dfef…9fc2
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
0xa4e9800f4e…fc4ab0
Audit this contract →
← previous block
·
next block →
recent activity