pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#91,085,372
← previous block
next block →
recent activity
Analyzing
Block #91,085,372
14 transactions · 14 stateful · 2026-07-28 14:47:25 UTC
Parallelism
86
/100
Blocked
7
%
Avg conflicts / tx
0.07
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#91,085,372
· 14 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
exactOutputSingle
#2
0xcbbdb31a
#3
0xab083028
#4
updatePrices
#5
0x5a5d9a99
#6
0x5a5d9a99
#7
updateDataFeedsValuesPartial
#8
batchUpdate
#9
execFwdPositionOps
#10
approve
#11
setData
#12
execOrders
· blocks 1
#13
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
12
w0
13
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc0eb79d1…29a4
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xefcdf197…96a2
0x34b655…2a6f
4 touches
1 conflict
0x4245e4e8…096e
0x000000…012a
2 touches
0 conflicts
0x00000000…0068
0x33927b…7f2f
2 touches
0 conflicts
0x00000000…0069
0x33927b…7f2f
2 touches
0 conflicts
0x00000000…006a
0x33927b…7f2f
2 touches
0 conflicts
0x00000000…006b
0x33927b…7f2f
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
0xc0eb79d1cb…5529a4
Audit this contract →
← previous block
·
next block →
recent activity