pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,586,455
← previous block
next block →
recent activity
Analyzing
Block #95,586,455
10 transactions · 9 stateful · 2026-08-13 08:43:10 UTC
Parallelism
60
/100
Blocked
33
%
Avg conflicts / tx
0.6
Longest chain
4
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,586,455
· 10 txs across 4 waves · depth 4
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
0x3f5c179b
#3
0x94defb17
· blocks 3
#7
execFwdPositionOps
#8
execFwdPositionOps
#9
setData
#4
0x94defb17
· blocks 2
#5
0x94defb17
· blocks 1
#6
0x94defb17
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
5
w2
6
w3
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd7a5592f…fe9e
0x968279…9342
8 touches
6 conflicts
0x521a5982…a82a
0x754704…b603
8 touches
6 conflicts
0x00000000…0006
0x968279…9342
8 touches
6 conflicts
0xc7f76214…a34e
0x968279…9342
8 touches
6 conflicts
0xc7f76214…a34f
0x968279…9342
8 touches
6 conflicts
0xc7f76214…a351
0x968279…9342
8 touches
6 conflicts
0xd7a5592f…fe97
0x968279…9342
8 touches
6 conflicts
0xd7a5592f…fe98
0x968279…9342
8 touches
6 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
6 conflicts on slot
0xd7a5592fdb…3ffe9e
Audit this contract →
← previous block
·
next block →
recent activity