pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#89,850,303
← previous block
next block →
recent activity
Analyzing
Block #89,850,303
13 transactions · 11 stateful · 2026-07-24 06:52:53 UTC
Parallelism
85
/100
Blocked
9
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#89,850,303
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
execFwdPositionOps
#3
executeBatch
#4
verifyOracleProofV2
#5
batchUpdate
#6
execFwdPositionOps
· blocks 1
#7
execOrders
#8
execOrders
#9
execOrders
#10
0x6a630c3d
#11
setData
#12
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
12
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2b5101ac…090b
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x438268c2…c848
0x34b655…2a6f
2 touches
0 conflicts
0x438268c2…c849
0x34b655…2a6f
2 touches
0 conflicts
0x451f3b2e…4b1b
0x34b655…2a6f
2 touches
0 conflicts
0x461f08a1…d183
0x34b655…2a6f
2 touches
0 conflicts
0x65104f89…bbce
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
0x2b5101acd1…7c090b
Audit this contract →
← previous block
·
next block →
recent activity