pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,968,921
← previous block
next block →
recent activity
Analyzing
Block #94,968,921
8 transactions · 7 stateful · 2026-08-11 04:42:39 UTC
Parallelism
63
/100
Blocked
29
%
Avg conflicts / tx
0.38
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,968,921
· 8 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
0x94defb17
#3
execFwdPositionOps
· blocks 2
#6
setData
#7
execOrders
#4
execFwdPositionOps
· blocks 1
#5
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
5
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa3a621f8…75a2
0x34b655…2a6f
6 touches
3 conflicts
0xaae6463e…bfcc
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0xffe7fbbe…9fa5
0x34b655…2a6f
6 touches
3 conflicts
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0x521a5982…a82a
0x754704…b603
2 touches
0 conflicts
0x00000000…0006
0x968279…9342
2 touches
0 conflicts
0x4ce2a459…3fb6
0x968279…9342
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
3 conflicts on slot
0xa3a621f8f3…6975a2
Audit this contract →
← previous block
·
next block →
recent activity