pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,972,914
← previous block
next block →
recent activity
Analyzing
Block #94,972,914
10 transactions · 9 stateful · 2026-08-11 05:02:44 UTC
Parallelism
80
/100
Blocked
11
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,972,914
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execFwdPositionOps
· blocks 1
#3
placeAndExecuteMarketSell
#4
verifyOracleProofV2
#5
execFwdPositionOps
#6
withdraw
#7
updateDataFeedsValuesPartial
#8
0x6a7aad6c
#9
setData
#2
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x19b340df…f4f0
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0xeca3f7cd…57b6
0x34b655…2a6f
4 touches
1 conflict
0xeca3f7cd…57b7
0x34b655…2a6f
4 touches
1 conflict
0x2b5101ac…090b
0x34b655…2a6f
4 touches
1 conflict
0xf10ad63b…3463
0x34b655…2a6f
4 touches
1 conflict
0xf3d10975…0d07
0x34b655…2a6f
4 touches
1 conflict
0x86b613c7…f98a
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
0x19b340df7f…6bf4f0
Audit this contract →
← previous block
·
next block →
recent activity