pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,528,352
← previous block
next block →
recent activity
Analyzing
Block #95,528,352
13 transactions · 12 stateful · 2026-08-13 03:50:56 UTC
Parallelism
77
/100
Blocked
17
%
Avg conflicts / tx
0.23
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,528,352
· 13 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0xd60faa87
#2
execOrders
#3
0x5acec890
#4
updateDataFeedsValuesPartial
#5
execFwdPositionOps
#6
0x94defb17
· blocks 2
#9
execFwdPositionOps
#10
0x57368ddf
#11
setData
#12
0x59558d29
#7
0x94defb17
· blocks 1
#8
0x94defb17
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
7
w1
8
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0006
0x968279…9342
6 touches
3 conflicts
0x0dac80cf…aca2
0x968279…9342
6 touches
3 conflicts
0x0dac80cf…aca3
0x968279…9342
6 touches
3 conflicts
0x0dac80cf…aca5
0x968279…9342
6 touches
3 conflicts
0xcbeabd5c…70ff
0x968279…9342
6 touches
3 conflicts
0xcbeabd5c…7100
0x968279…9342
6 touches
3 conflicts
0xcbeabd5c…7103
0x968279…9342
6 touches
3 conflicts
0xcbeabd5c…7104
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
0x0000000000…000006
Audit this contract →
← previous block
·
next block →
recent activity