pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,123,540
← previous block
next block →
recent activity
Analyzing
Block #95,123,540
11 transactions · 10 stateful · 2026-08-11 17:41:14 UTC
Parallelism
82
/100
Blocked
10
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,123,540
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
0x5acec890
#3
updateDataFeedsValuesPartial
#4
0xae92a63a
#5
execOrders
#6
execFwdPositionOps
#7
0x6a7b5f31
#8
setData
#9
execOrders
· blocks 1
#10
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
9
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x54526994…55b2
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x1825deaa…f973
0x09475a…400f
2 touches
0 conflicts
0x00000000…0002
0x1c8a33…d316
2 touches
0 conflicts
0x36a76bd2…1fb0
0x34b655…2a6f
2 touches
0 conflicts
0x5e0b8bbe…377b
0x34b655…2a6f
2 touches
0 conflicts
0x5eb187dd…b1d6
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
0x5452699410…4155b2
Audit this contract →
← previous block
·
next block →
recent activity