pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#89,694,430
← previous block
next block →
recent activity
Analyzing
Block #89,694,430
13 transactions · 11 stateful · 2026-07-23 17:46:12 UTC
Parallelism
77
/100
Blocked
18
%
Avg conflicts / tx
0.15
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#89,694,430
· 13 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
exec
#2
0xab083028
· blocks 1
#4
execPerpOps
#5
updateDataFeedsValuesPartial
#6
execFwdPositionOps
#8
execFwdPositionOps
#9
0x6a6253db
#10
transfer
#11
setData
#12
execOrders
#3
0x6ad2e98b
· blocks 1
#7
0x3f5c179b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
7
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0x6ccf5c86…9954
0x851145…3f07
4 touches
1 conflict
0x77a99df7…d784
0x851145…3f07
4 touches
1 conflict
0xb05cd4f5…73d0
0x2b46c0…1669
2 touches
0 conflicts
0xdb067026…9eb8
0x2b46c0…1669
2 touches
0 conflicts
0xf6cc7de8…0b4a
0x3bd359…433a
2 touches
0 conflicts
0x00000000…0000
0x63e48b…53f2
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:
Kuru Exchange: MarginAccount
1 conflict on slot
0x889d5e90c7…59929a
Audit this contract →
← previous block
·
next block →
recent activity