pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#87,285,558
← previous block
next block →
recent activity
Analyzing
Block #87,285,558
10 transactions · 8 stateful · 2026-07-12 14:16:51 UTC
Parallelism
70
/100
Blocked
25
%
Avg conflicts / tx
0.3
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#87,285,558
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
addLiquidityNATIVE
#2
0x0f6795d9
· blocks 2
#5
updateDataFeedsValuesPartial
#6
updatePriceFeedsIfNecessary
#7
0x0f6795d9
#8
0x6a53a24b
#9
setData
#3
0x0f6795d9
· blocks 1
#4
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
4
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x016f88ec…46fc
0x34b655…2a6f
6 touches
3 conflicts
0xeab8b522…d3e6
0x34b655…2a6f
4 touches
1 conflict
0x1353affc…75e0
0x34b655…2a6f
4 touches
1 conflict
0x27b5413c…c0e7
0x5afd3e…7620
2 touches
0 conflicts
0x00000000…0006
0x60bb42…87ea
2 touches
0 conflicts
0x4039b31f…0f4a
0x754704…b603
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
0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block
·
next block →
recent activity