pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,024,859
← previous block
next block →
recent activity
Analyzing
Block #96,024,859
11 transactions · 8 stateful · 2026-08-14 21:29:46 UTC
Parallelism
82
/100
Blocked
25
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,024,859
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x6ad2e98b
#2
execPerpOps
#3
execPerpOps
#4
updateDataFeedsValuesPartial
#5
execFwdPositionOpsV2
· blocks 1
#6
0x94defb17
· blocks 1
#9
updateTemporalNumericValuesV1
#10
setData
#7
0x94defb17
#8
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w0
7
w1
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe9e0535d…c39c
0x968279…9342
4 touches
1 conflict
0x00000000…0006
0x968279…9342
4 touches
1 conflict
0xbfc514c2…37db
0x968279…9342
4 touches
1 conflict
0xbfc514c2…37dc
0x968279…9342
4 touches
1 conflict
0xbfc514c2…37de
0x968279…9342
4 touches
1 conflict
0xe9e0535d…c395
0x968279…9342
4 touches
1 conflict
0xe9e0535d…c396
0x968279…9342
4 touches
1 conflict
0xe9e0535d…c399
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
0xe9e0535ddb…22c39c
Audit this contract →
← previous block
·
next block →
recent activity