pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#89,377,443
← previous block
next block →
recent activity
Analyzing
Block #89,377,443
10 transactions · 10 stateful · 2026-07-22 07:29:10 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,377,443
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execFwdPositionOps
· blocks 1
#2
batchUpdate
#3
execFwdPositionOps
#4
forward
#6
updateDataFeedsValuesPartial
#7
prepareQuestion
#8
setData
#9
execOrders
#5
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x70986451…c6bd
0x34b655…2a6f
4 touches
1 conflict
0xc7954a60…d294
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x021afc04…da69
0x34b655…2a6f
2 touches
0 conflicts
0x021afc04…da6a
0x34b655…2a6f
2 touches
0 conflicts
0x078f38b5…2eaa
0x34b655…2a6f
2 touches
0 conflicts
0x0ba8d6a8…28c6
0x34b655…2a6f
2 touches
0 conflicts
0x103f63b2…ff11
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
0x7098645134…3ac6bd
Audit this contract →
← previous block
·
next block →
recent activity