pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#89,710,607
← previous block
next block →
recent activity
Analyzing
Block #89,710,607
10 transactions · 10 stateful · 2026-07-23 19:07:43 UTC
Parallelism
80
/100
Blocked
10
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#89,710,607
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5a5d9a99
#2
updateDataFeedsValuesPartial
#3
execFwdPositionOps
· blocks 1
#4
execFwdPositionOps
· blocks 1
#5
commit
#7
0x6a6266f6
#8
setData
#9
execOrder
#6
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3e0ef032…8627
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0xf3d10975…0d07
0x34b655…2a6f
4 touches
1 conflict
0x59dccbd8…2bf6
0x34b655…2a6f
4 touches
1 conflict
0x085e35d2…8d1f
0x34b655…2a6f
2 touches
0 conflicts
0x085e35d2…8d20
0x34b655…2a6f
2 touches
0 conflicts
0x0b0611f7…e63a
0x34b655…2a6f
2 touches
0 conflicts
0x0c172c8a…3dad
0x34b655…2a6f
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
0x3e0ef03248…a08627
Audit this contract →
← previous block
·
next block →
recent activity