pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,277,663
← previous block
next block →
recent activity
Analyzing
Block #95,277,663
13 transactions · 13 stateful · 2026-08-12 06:45:20 UTC
Parallelism
85
/100
Blocked
15
%
Avg conflicts / tx
0.15
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,277,663
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrders
#2
updatePrices
#3
execFwdPositionOps
· blocks 1
#4
execOrders
· blocks 1
#7
execFwdPositionOps
#8
updateDataFeedsValuesPartial
#9
commit
#10
setData
#11
0x59558d29
#12
execOrders
#5
execFwdPositionOps
#6
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w0
5
w1
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x730c8155…0856
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0xfe61a5ca…e462
0x34b655…2a6f
4 touches
1 conflict
0x0ed7cc0b…ee52
0x34b655…2a6f
4 touches
1 conflict
0x5890dedf…54c9
0x34b655…2a6f
3 touches
1 conflict
0x21e4c12d…0c4c
0x34b655…2a6f
2 touches
0 conflicts
0x64a785e4…0110
0x34b655…2a6f
2 touches
0 conflicts
0x734ee320…caae
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
0x730c81554f…1e0856
Audit this contract →
← previous block
·
next block →
recent activity