pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#89,536,760
← previous block
next block →
recent activity
Analyzing
Block #89,536,760
14 transactions · 13 stateful · 2026-07-23 01:13:40 UTC
Parallelism
86
/100
Blocked
15
%
Avg conflicts / tx
0.14
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#89,536,760
· 14 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5a5d9a99
#2
0x5a5d9a99
#3
sell
· blocks 1
#5
updateDataFeedsValuesPartial
#6
updateDataFeedsValuesPartial
#7
execFwdPositionOps
· blocks 1
#9
0x57368ddf
#10
forward
#11
setData
#12
execOrders
#13
0xc7e3ec2c
#4
sell
#8
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
7
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6411bf1f…b7de
0x9ddae8…fb60
4 touches
1 conflict
0xaa2db50e…43a8
0x3bd359…433a
4 touches
1 conflict
0x00000000…0000
0x51cbec…7b78
4 touches
1 conflict
0x00000000…0003
0x51cbec…7b78
4 touches
1 conflict
0x00000000…0004
0x51cbec…7b78
4 touches
1 conflict
0x13f654fc…8882
0x34b655…2a6f
4 touches
1 conflict
0x1b2b9858…8f12
0x34b655…2a6f
4 touches
1 conflict
0x5866aa50…fe80
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:
0x9ddae80a…d5fb60
1 conflict on slot
0x6411bf1f01…58b7de
Audit this contract →
← previous block
·
next block →
recent activity