pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#87,615,265
← previous block
next block →
recent activity
Analyzing
Block #87,615,265
10 transactions · 8 stateful · 2026-07-14 03:02:34 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,615,265
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
updatePrices
#3
0x5a5d9a99
· blocks 1
#5
updateDataFeedsValuesPartial
#6
0x5339c59f
#7
setData
#8
0x979756…d1ae
#9
0x39435dac
#4
0x5a5d9a99
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5170a218…3a84
0xc8689a…ee79
4 touches
1 conflict
0x07f69062…03ec
0x34b655…2a6f
4 touches
1 conflict
0x1175233a…64e7
0x34b655…2a6f
4 touches
1 conflict
0x25329a48…4e00
0x34b655…2a6f
4 touches
1 conflict
0x2fbb25e7…87d3
0x34b655…2a6f
4 touches
1 conflict
0x68b75835…d6f3
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0xa0af25f7…9129
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: Settlement / Helper
1 conflict on slot
0x5170a2184f…f03a84
Audit this contract →
← previous block
·
next block →
recent activity