pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#89,402,046
← previous block
next block →
recent activity
Analyzing
Block #89,402,046
7 transactions · 5 stateful · 2026-07-22 10:13:41 UTC
Parallelism
71
/100
Blocked
20
%
Avg conflicts / tx
0.14
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#89,402,046
· 7 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
updateDataFeedsValuesPartial
#3
execFwdPositionOps
· blocks 1
#5
setData
#6
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
0xf2db28fa…4ab2
0x34b655…2a6f
4 touches
1 conflict
0x091164f5…6e33
0x34b655…2a6f
4 touches
1 conflict
0x1d4418c0…6d18
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x50e37662…cc85
0x34b655…2a6f
4 touches
1 conflict
0x9f106d29…9662
0x34b655…2a6f
4 touches
1 conflict
0x9f4bc324…e6a6
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
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
0xf2db28fa73…984ab2
Audit this contract →
← previous block
·
next block →
recent activity