pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,023,811
← previous block
next block →
recent activity
Analyzing
Block #96,023,811
8 transactions · 6 stateful · 2026-08-14 21:24:30 UTC
Parallelism
75
/100
Blocked
33
%
Avg conflicts / tx
0.25
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,023,811
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execFwdPositionOpsV2
· blocks 1
#2
execFwdPositionOpsV2
#3
updateDataFeedsValuesPartial
#4
setData
#5
0x94defb17
· blocks 1
#6
0x94defb17
#7
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
5
w0
6
w1
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xee19a375…e32f
0x968279…9342
4 touches
1 conflict
0x00000000…0006
0x968279…9342
4 touches
1 conflict
0x3732369d…3c7f
0x968279…9342
4 touches
1 conflict
0x3732369d…3c80
0x968279…9342
4 touches
1 conflict
0x3732369d…3c83
0x968279…9342
4 touches
1 conflict
0x3732369d…3c84
0x968279…9342
4 touches
1 conflict
0x3732369d…3c86
0x968279…9342
4 touches
1 conflict
0xee19a375…e32c
0x968279…9342
4 touches
1 conflict
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
1 conflict on slot
0xee19a375d2…03e32f
Audit this contract →
← previous block
·
next block →
recent activity