pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,356,721
← previous block
next block →
recent activity
Analyzing
Block #95,356,721
12 transactions · 9 stateful · 2026-08-12 13:25:33 UTC
Parallelism
83
/100
Blocked
11
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,356,721
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
0x6a7c74c5
#3
0x5acec890
#4
updateDataFeedsValuesPartial
#5
execFwdPositionOps
· blocks 1
#7
0x3f5c179b
#8
forward
#9
setData
#10
0xca5b02…bfe8
#11
0x59558d29
#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
0xb1b58b33…874f
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x071ff290…ec09
0x34b655…2a6f
2 touches
0 conflicts
0x12659c8c…062e
0x34b655…2a6f
2 touches
0 conflicts
0x1a5d321d…a474
0x34b655…2a6f
2 touches
0 conflicts
0x34d95d94…3a16
0x34b655…2a6f
2 touches
0 conflicts
0x4a5956ef…e226
0x34b655…2a6f
2 touches
0 conflicts
0x594dd01b…6c8b
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
0xb1b58b3385…e4874f
Audit this contract →
← previous block
·
next block →
recent activity