pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,301,726
← previous block
next block →
recent activity
Analyzing
Block #95,301,726
14 transactions · 12 stateful · 2026-08-12 08:46:54 UTC
Parallelism
86
/100
Blocked
8
%
Avg conflicts / tx
0.07
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,301,726
· 14 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
transferAndMulticall
#2
updateDataFeedsValuesPartial
#3
execFwdPositionOps
· blocks 1
#5
execFwdPositionOps
#6
setData
#7
0xe9c13b…164a
#8
execOrders
#9
execOrders
#10
execOrders
#11
execOrders
#12
execOrders
#13
execOrders
#4
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x19795ad6…4a16
0x34b655…2a6f
4 touches
1 conflict
0x37eb23c7…4160
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x23731bc0…de34
0x0c65a0…0852
2 touches
0 conflicts
0x85946e90…7fd6
0x0c65a0…0852
2 touches
0 conflicts
0xad193a14…a3a6
0x0c65a0…0852
2 touches
0 conflicts
0x3de215fe…c018
0x3bd359…433a
2 touches
0 conflicts
0xc5c4c1d1…2145
0x3bd359…433a
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
0x19795ad604…434a16
Audit this contract →
← previous block
·
next block →
recent activity