pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#89,771,486
← previous block
next block →
recent activity
Analyzing
Block #89,771,486
10 transactions · 9 stateful · 2026-07-24 00:15:11 UTC
Parallelism
70
/100
Blocked
22
%
Avg conflicts / tx
0.3
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#89,771,486
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x1a945f9c
#2
updateDataFeedsValuesPartial
#3
withdraw
#4
execFwdPositionOps
· blocks 2
#6
execOrders
#8
0x6a62af06
#9
setData
#5
execFwdPositionOps
· blocks 1
#7
execOrder
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
7
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x74f95963…01a2
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0070
0x1efe02…37d6
2 touches
0 conflicts
0x3e1b36d2…7073
0x1efe02…37d6
2 touches
0 conflicts
0x67c7e5da…e6e9
0x1efe02…37d6
2 touches
0 conflicts
0xfd0a3169…b7e5
0x1efe02…37d6
2 touches
0 conflicts
0x00bac013…a28c
0x91b81b…6d56
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
3 conflicts on slot
0x482471adbb…39122f
Audit this contract →
← previous block
·
next block →
recent activity