pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#89,681,722
← previous block
next block →
recent activity
Analyzing
Block #89,681,722
10 transactions · 9 stateful · 2026-07-23 16:42:05 UTC
Parallelism
80
/100
Blocked
11
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#89,681,722
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5a5d9a99
#2
0x5a5d9a99
· blocks 1
#3
execFwdPositionOps
#4
updateDataFeedsValuesPartial
#5
updateDataFeedsValuesPartial
#6
permit2TransferAndMulticall
#8
0x6a6244d5
#9
setData
#7
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc948dbdc…199a
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0x0090639e…243e
0x34b655…2a6f
2 touches
0 conflicts
0x1546e1b4…1e15
0x34b655…2a6f
2 touches
0 conflicts
0x16e1bce0…73a5
0x34b655…2a6f
2 touches
0 conflicts
0x1730ab3c…ce37
0x34b655…2a6f
2 touches
0 conflicts
0x1ffbc5c9…461f
0x34b655…2a6f
2 touches
0 conflicts
0x24b6091e…d294
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
0xc948dbdcb8…f4199a
Audit this contract →
← previous block
·
next block →
recent activity