pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,564,315
← previous block
next block →
recent activity
Analyzing
Block #95,564,315
10 transactions · 7 stateful · 2026-08-13 06:51:49 UTC
Parallelism
80
/100
Blocked
14
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,564,315
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
transfer
#3
0x5acec890
#4
updateDataFeedsValuesPartial
#5
execFwdPositionOps
· blocks 1
#7
execFwdPositionOps
#8
transfer
#9
setData
#6
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf85bdc12…5dff
0x34b655…2a6f
4 touches
1 conflict
0x24602217…9af8
0x34b655…2a6f
4 touches
1 conflict
0x78860c4f…cade
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x0728ec77…146c
0x34b655…2a6f
2 touches
0 conflicts
0x0b1d86ea…d766
0x34b655…2a6f
2 touches
0 conflicts
0x362894e6…669f
0x34b655…2a6f
2 touches
0 conflicts
0x362894e6…66a0
0x34b655…2a6f
2 touches
0 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:
Perpl
1 conflict on slot
0xf85bdc12e0…265dff
Audit this contract →
← previous block
·
next block →
recent activity