pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,579,473
← previous block
next block →
recent activity
Analyzing
Block #95,579,473
13 transactions · 11 stateful · 2026-08-13 08:08:03 UTC
Parallelism
85
/100
Blocked
9
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,579,473
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execPerpOps
#2
execPerpOps
#3
0xb2d4797b
#4
updateDataFeedsValuesPartial
#5
execFwdPositionOps
#6
0x3f5c179b
#7
execFwdPositionOps
#8
0x94defb17
· blocks 1
#10
execFwdPositionOps
#11
setData
#12
0x59558d29
#9
0x94defb17
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
8
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd90b8752…97f6
0x968279…9342
4 touches
1 conflict
0x521a5982…a82a
0x754704…b603
4 touches
1 conflict
0x00000000…0006
0x968279…9342
4 touches
1 conflict
0xcbd83a2f…5cd7
0x968279…9342
4 touches
1 conflict
0xcbd83a2f…5cd8
0x968279…9342
4 touches
1 conflict
0xcbd83a2f…5cda
0x968279…9342
4 touches
1 conflict
0xd90b8752…97ef
0x968279…9342
4 touches
1 conflict
0xd90b8752…97f0
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
0xd90b87522a…f397f6
Audit this contract →
← previous block
·
next block →
recent activity