pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#89,519,537
← previous block
next block →
recent activity
Analyzing
Block #89,519,537
9 transactions · 8 stateful · 2026-07-22 23:18:43 UTC
Parallelism
78
/100
Blocked
13
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#89,519,537
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
updateDataFeedsValuesPartial
#3
execFwdPositionOps
· blocks 1
#4
batchUpdate
#6
execOrders
#7
0x6a61504b
#8
setData
#5
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7256824b…b16e
0x34b655…2a6f
4 touches
1 conflict
0xb900efa2…8624
0x34b655…2a6f
4 touches
1 conflict
0xf51ec09c…b4a9
0x34b655…2a6f
4 touches
1 conflict
0x846f2172…fd54
0x0555e3…2b9c
2 touches
0 conflicts
0xbb371eab…3efc
0x0555e3…2b9c
2 touches
0 conflicts
0x66de0ce3…337a
0x188d58…ea8e
2 touches
0 conflicts
0x66de0ce3…337b
0x188d58…ea8e
2 touches
0 conflicts
0x00000000…0012
0x1b6862…e19c
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
0x7256824be2…3eb16e
Audit this contract →
← previous block
·
next block →
recent activity