pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#89,880,384
← previous block
next block →
recent activity
Analyzing
Block #89,880,384
12 transactions · 11 stateful · 2026-07-24 09:24:12 UTC
Parallelism
83
/100
Blocked
9
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#89,880,384
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
updatePrices
#3
updateDataFeedsValuesPartial
#4
execFwdPositionOps
#5
0x3f5c179b
#6
0x0c7abd22
#7
forward
#8
execFwdPositionOps
· blocks 1
#10
setData
#11
execOrders
#9
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
8
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaec27a46…c334
0x34b655…2a6f
4 touches
1 conflict
0xaffb690e…61d0
0x34b655…2a6f
4 touches
1 conflict
0xaffb690e…61d1
0x34b655…2a6f
4 touches
1 conflict
0xc482682b…5a12
0x34b655…2a6f
4 touches
1 conflict
0xff28ee17…414e
0x34b655…2a6f
4 touches
1 conflict
0x4b77c415…75b0
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0xa8fbe63b…a8ed
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
1 conflict on slot
0xaec27a468a…7cc334
Audit this contract →
← previous block
·
next block →
recent activity