pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,598,035
← previous block
next block →
recent activity
Analyzing
Block #95,598,035
10 transactions · 8 stateful · 2026-08-13 09:41:25 UTC
Parallelism
80
/100
Blocked
25
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,598,035
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrder
· blocks 1
#3
exactInputSingle
#4
0x3f5c179b
#5
execFwdPositionOps
· blocks 1
#7
updateDataFeedsValuesPartial
#8
transfer
#9
setData
#2
execOrders
#6
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfb9f51f4…0f16
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x734ee320…caae
0x34b655…2a6f
4 touches
1 conflict
0x1ea0a6bc…6a74
0x2a68ba…90c5
2 touches
0 conflicts
0x0672e4a2…8d1f
0x34b655…2a6f
2 touches
0 conflicts
0x70e3da66…674a
0x34b655…2a6f
2 touches
0 conflicts
0x7de57974…f5ba
0x34b655…2a6f
2 touches
0 conflicts
0x8b03f143…6e36
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
0xfb9f51f42d…620f16
Audit this contract →
← previous block
·
next block →
recent activity