pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,406,688
← previous block
next block →
recent activity
Analyzing
Block #95,406,688
12 transactions · 10 stateful · 2026-08-12 17:38:28 UTC
Parallelism
83
/100
Blocked
10
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,406,688
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
exactInputSingle
#2
0x0c7abd22
#3
0x8263f5d9
#4
execOrders
· blocks 1
#5
updateDataFeedsValuesPartial
#7
0x3f5c179b
#8
0x57368ddf
#9
0xed82b078
#10
setData
#11
0x59558d29
#6
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8046ca3c…f094
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0xb1632c2f…d991
0x0a3323…0a3c
2 touches
0 conflicts
0xfea142d7…d423
0x0a3323…0a3c
2 touches
0 conflicts
0x00000000…0012
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0013
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0015
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…001f
0x1b6862…e19c
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
0x8046ca3cb2…45f094
Audit this contract →
← previous block
·
next block →
recent activity