pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#87,286,679
← previous block
next block →
recent activity
Analyzing
Block #87,286,679
10 transactions · 9 stateful · 2026-07-12 14:24:21 UTC
Parallelism
70
/100
Blocked
22
%
Avg conflicts / tx
0.2
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#87,286,679
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
updatePrices
#2
0x5a5d9a99
#3
updateDataFeedsValuesPartial
#4
updateDataFeedsValuesPartial
#5
execute
#6
execFwdPositionOps
· blocks 1
#7
setData
#8
execFwdPositionOps
· blocks 1
#9
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
8
w1
9
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbf78ee7f…e7fd
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0002
0x04fdea…47d7
2 touches
0 conflicts
0x258fcaf5…2084
0x34b655…2a6f
2 touches
0 conflicts
0x664bf99e…0a8c
0x34b655…2a6f
2 touches
0 conflicts
0x845ec8b0…c1af
0x34b655…2a6f
2 touches
0 conflicts
0x9a36cb2e…0929
0x34b655…2a6f
2 touches
0 conflicts
0x01a89030…f786
0x368ee5…7ca4
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
0xbf78ee7fb5…b5e7fd
Audit this contract →
← previous block
·
next block →
recent activity