pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#89,870,773
← previous block
next block →
recent activity
Analyzing
Block #89,870,773
7 transactions · 5 stateful · 2026-07-24 08:35:51 UTC
Parallelism
71
/100
Blocked
20
%
Avg conflicts / tx
0.14
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#89,870,773
· 7 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
execPerpOps
#3
execPerpOps
#4
updateDataFeedsValuesPartial
#5
execFwdPositionOps
· blocks 1
#6
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaa9f27b0…9cf2
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x08cc68a2…2a59
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x81561f70…fefd
0x34b655…2a6f
4 touches
1 conflict
0x03b80be8…1214
0x34b655…2a6f
2 touches
0 conflicts
0x1959e50b…e9bb
0x34b655…2a6f
2 touches
0 conflicts
0x1d351a9b…f2dd
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
0xaa9f27b038…bb9cf2
Audit this contract →
← previous block
·
next block →
recent activity