pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#89,701,616
← previous block
next block →
recent activity
Analyzing
Block #89,701,616
11 transactions · 9 stateful · 2026-07-23 18:22:23 UTC
Parallelism
82
/100
Blocked
11
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#89,701,616
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
0x5a5d9a99
#3
execFwdPositionOps
· blocks 1
#5
execFwdPositionOps
#6
updateDataFeedsValuesPartial
#7
0x3f5c179b
#8
0x3f5c179b
#9
execOrders
#10
setData
#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
0x81561f70…fefd
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xadc92aaf…3077
0x34b655…2a6f
4 touches
1 conflict
0x487402a1…90b7
0x34b655…2a6f
4 touches
1 conflict
0x487402a1…90b8
0x34b655…2a6f
4 touches
1 conflict
0x16b2c220…a431
0x34b655…2a6f
4 touches
1 conflict
0x620a4cf0…c6ae
0x34b655…2a6f
4 touches
1 conflict
0x7aad02c6…b979
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
0x81561f70ba…26fefd
Audit this contract →
← previous block
·
next block →
recent activity