pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#89,826,334
← previous block
next block →
recent activity
Analyzing
Block #89,826,334
10 transactions · 10 stateful · 2026-07-24 04:51:59 UTC
Parallelism
80
/100
Blocked
10
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#89,826,334
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
execFwdPositionOps
· blocks 1
#3
executeBatch
#4
execFwdPositionOps
#5
execOrders
#7
withdrawReserve
#8
setData
#9
execOrders
#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
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x3dcc92f2…f562
0x34b655…2a6f
2 touches
0 conflicts
0x8d15d872…fa53
0x34b655…2a6f
2 touches
0 conflicts
0xa7c7dd7e…ce22
0x34b655…2a6f
2 touches
0 conflicts
0xc6bb7e6c…bf35
0x34b655…2a6f
2 touches
0 conflicts
0xec7d120d…7084
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
0x92385428ad…dc6941
Audit this contract →
← previous block
·
next block →
recent activity