pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#88,158,265
← previous block
next block →
recent activity
Analyzing
Block #88,158,265
12 transactions · 9 stateful · 2026-07-16 15:34:46 UTC
Parallelism
83
/100
Blocked
11
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#88,158,265
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
updateDataFeedsValuesPartial
#3
updateDataFeedsValuesPartial
#4
execFwdPositionOps
#5
execFwdPositionOps
#6
execFwdPositionOps
#7
commit
#8
setData
#9
0x34653439
#10
execOrders
· blocks 1
#11
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
10
w0
11
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x634daab4…dd5e
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x1bd69a6a…2b8a
0x34b655…2a6f
4 touches
1 conflict
0x054d372a…784e
0x34b655…2a6f
2 touches
0 conflicts
0x08636046…e60f
0x34b655…2a6f
2 touches
0 conflicts
0x184b47c9…59df
0x34b655…2a6f
2 touches
0 conflicts
0x30fce83f…a1d6
0x34b655…2a6f
2 touches
0 conflicts
0x4ae3b148…7ed2
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
0x634daab4a2…5edd5e
Audit this contract →
← previous block
·
next block →
recent activity