pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,960,853
← previous block
next block →
recent activity
Analyzing
Block #94,960,853
11 transactions · 10 stateful · 2026-08-11 04:02:05 UTC
Parallelism
82
/100
Blocked
10
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,960,853
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xa96df62f
#2
0x7d2c3ba9
#3
0x5acec890
· blocks 1
#5
execFwdPositionOps
#6
updateDataFeedsValuesPartial
#7
placeAndExecuteMarketBuy
#8
0x6a7a9f35
#9
setData
#10
depositTo
#4
execFwdPositionOps
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
0xac3e4969…39e9
0x34b655…2a6f
4 touches
1 conflict
0x45ea7a97…bbb3
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x31f646a7…9f30
0x000000…012a
2 touches
0 conflicts
0x354fd20e…e963
0x000000…012a
2 touches
0 conflicts
0xe7fa6db5…a6d4
0x000000…012a
2 touches
0 conflicts
0xada50131…9e7d
0x0b0a7a…aeb0
2 touches
0 conflicts
0x08e8f2c9…a11a
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
0xac3e4969cf…1739e9
Audit this contract →
← previous block
·
next block →
recent activity