pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,022,505
← previous block
next block →
recent activity
Analyzing
Block #96,022,505
11 transactions · 10 stateful · 2026-08-14 21:17:56 UTC
Parallelism
73
/100
Blocked
30
%
Avg conflicts / tx
0.36
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,022,505
· 11 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x0c7abd22
#2
0x5acec890
#3
depositNative
#4
execFwdPositionOpsV2
· blocks 1
#5
0x94defb17
· blocks 2
#8
execFwdPositionOpsV2
#10
setData
#6
0x94defb17
· blocks 1
#9
execFwdPositionOpsV2
#7
0x94defb17
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w0
6
w1
7
w2
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdcb3892e…a96d
0x968279…9342
6 touches
3 conflicts
0x521a5982…a82a
0x754704…b603
6 touches
3 conflicts
0x00000000…0006
0x968279…9342
6 touches
3 conflicts
0xb7090389…c321
0x968279…9342
6 touches
3 conflicts
0xb7090389…c322
0x968279…9342
6 touches
3 conflicts
0xb7090389…c325
0x968279…9342
6 touches
3 conflicts
0xb7090389…c326
0x968279…9342
6 touches
3 conflicts
0xb7090389…c328
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
0xdcb3892e90…b2a96d
Audit this contract →
← previous block
·
next block →
recent activity