pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,088,178
← previous block
next block →
recent activity
Analyzing
Block #96,088,178
8 transactions · 8 stateful · 2026-08-15 02:48:16 UTC
Parallelism
75
/100
Blocked
13
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,088,178
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execFwdPositionOpsV2
#2
execFwdPositionOpsV2
· blocks 1
#3
verifyOracleProofV2
#5
updateDataFeedsValuesPartial
#6
updateDataFeedsValuesPartial
#7
setData
#4
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xafb8e71e…9285
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x1088dfef…9fc2
0x34b655…2a6f
2 touches
0 conflicts
0x40a9339c…6571
0x34b655…2a6f
2 touches
0 conflicts
0x40a9339c…6572
0x34b655…2a6f
2 touches
0 conflicts
0x40c106b6…b695
0x34b655…2a6f
2 touches
0 conflicts
0x4f858307…7642
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
0xafb8e71eb0…ec9285
Audit this contract →
← previous block
·
next block →
recent activity