pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,086,671
← previous block
next block →
recent activity
Analyzing
Block #96,086,671
11 transactions · 10 stateful · 2026-08-15 02:40:41 UTC
Parallelism
73
/100
Blocked
40
%
Avg conflicts / tx
0.45
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,086,671
· 11 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
execFwdPositionOpsV2
· blocks 1
#2
updateDataFeedsValuesPartial
#4
0x94defb17
· blocks 2
#7
setData
#8
execOrders
· blocks 1
#10
execOrders
#3
execFwdPositionOpsV2
#5
0x94defb17
· blocks 1
#9
execOrders
#6
0x94defb17
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w1
4
w0
5
w1
6
w2
8
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe6b9f9a4…adbf
0x968279…9342
6 touches
3 conflicts
0x521a5982…a82a
0x754704…b603
6 touches
3 conflicts
0x00000000…0006
0x968279…9342
6 touches
3 conflicts
0xabbdcd04…dd9d
0x968279…9342
6 touches
3 conflicts
0xabbdcd04…dd9e
0x968279…9342
6 touches
3 conflicts
0xabbdcd04…dda1
0x968279…9342
6 touches
3 conflicts
0xabbdcd04…dda2
0x968279…9342
6 touches
3 conflicts
0xabbdcd04…dda3
0x968279…9342
6 touches
3 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:
0x96827978…f09342
3 conflicts on slot
0xe6b9f9a4dc…c1adbf
Audit this contract →
← previous block
·
next block →
recent activity