pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#89,769,849
← previous block
next block →
recent activity
Analyzing
Block #89,769,849
10 transactions · 10 stateful · 2026-07-24 00:06:56 UTC
Parallelism
70
/100
Blocked
30
%
Avg conflicts / tx
0.5
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#89,769,849
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
execFwdPositionOps
· blocks 2
#3
execFwdPositionOps
· blocks 1
#5
execOrders
#7
setData
#8
execOrders
· blocks 1
#4
execFwdPositionOps
· blocks 1
#9
execOrders
#6
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w0
4
w1
6
w2
8
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf29db88e…d471
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6426
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xeab8b522…d3e6
0x34b655…2a6f
4 touches
1 conflict
0x2fcaf77d…8bec
0x34b655…2a6f
4 touches
1 conflict
0x35b89cd8…5092
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
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:
Perpl
3 conflicts on slot
0xf29db88e1c…b6d471
Audit this contract →
← previous block
·
next block →
recent activity