pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#87,313,391
← previous block
next block →
recent activity
Analyzing
Block #87,313,391
10 transactions · 8 stateful · 2026-07-12 17:22:55 UTC
Parallelism
80
/100
Blocked
13
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#87,313,391
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
permit2TransferAndMulticall
#3
updateDataFeedsValuesPartial
#4
execFwdPositionOps
· blocks 1
#6
0x6a53cde7
#7
setData
#8
0xb8024e41
#9
0xc7e3ec2c
#5
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa013ecc1…7c8f
0x34b655…2a6f
4 touches
1 conflict
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0002
0x04fdea…47d7
2 touches
0 conflicts
0xb1a0dd74…f087
0x188d58…ea8e
2 touches
0 conflicts
0x0886e12a…1c48
0x34b655…2a6f
2 touches
0 conflicts
0x0a2131b3…455e
0x34b655…2a6f
2 touches
0 conflicts
0x1ba5d36c…9336
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
0xa013ecc17b…017c8f
Audit this contract →
← previous block
·
next block →
recent activity