pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#87,903,468
← previous block
next block →
recent activity
Analyzing
Block #87,903,468
15 transactions · 13 stateful · 2026-07-15 11:10:18 UTC
Parallelism
80
/100
Blocked
15
%
Avg conflicts / tx
0.2
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#87,903,468
· 15 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
repay
#2
execPerpOps
#3
execPerpOps
#4
0x5a5d9a99
#5
0x98717539
#6
approve
#7
execFwdPositionOps
· blocks 2
#10
updateDataFeedsValuesPartial
#11
updateDataFeedsValuesPartial
#12
forward
#13
0x6a576b11
#14
setData
#8
execFwdPositionOps
· blocks 1
#9
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
7
w0
8
w1
9
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x3b223675…d6f6
0x111111…db61
2 touches
0 conflicts
0x52f2c419…6085
0x111111…db61
2 touches
0 conflicts
0x00000000…0000
0x2970fd…1fc2
2 touches
0 conflicts
0x00000000…000a
0x2d8bbb…026a
2 touches
0 conflicts
0x00000000…0005
0x3249df…c0f6
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
3 conflicts on slot
0x0733be30d6…38112f
Audit this contract →
← previous block
·
next block →
recent activity