pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,277,802
← previous block
next block →
recent activity
Analyzing
Block #95,277,802
7 transactions · 6 stateful · 2026-08-12 06:46:01 UTC
Parallelism
71
/100
Blocked
17
%
Avg conflicts / tx
0.14
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,277,802
· 7 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execFwdPositionOps
#2
execFwdPositionOps
· blocks 1
#3
updateDataFeedsValuesPartial
#4
0x6a7c1721
#5
setData
#6
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x99701186…1cbf
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x155e52ca…fac7
0x34b655…2a6f
2 touches
0 conflicts
0x442e26a3…e968
0x34b655…2a6f
2 touches
0 conflicts
0x4abfb389…18f4
0x34b655…2a6f
2 touches
0 conflicts
0x540028d7…83af
0x34b655…2a6f
2 touches
0 conflicts
0x5fd97c7b…b1fa
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
0x997011860a…ad1cbf
Audit this contract →
← previous block
·
next block →
recent activity