pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#87,257,349
← previous block
next block →
recent activity
Analyzing
Block #87,257,349
9 transactions · 9 stateful · 2026-07-12 11:08:16 UTC
Parallelism
78
/100
Blocked
11
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#87,257,349
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
updateDataFeedsValuesPartial
#3
0x0f6795d9
· blocks 1
#5
0x0f6795d9
#6
0x6a537618
#7
setData
#8
0x39435dac
#4
0x0f6795d9
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
0xae901867…8085
0x34b655…2a6f
4 touches
1 conflict
0xae901867…8086
0x34b655…2a6f
4 touches
1 conflict
0x0d36fa01…b9ca
0x34b655…2a6f
2 touches
0 conflicts
0x179fd795…fbe5
0x34b655…2a6f
2 touches
0 conflicts
0x1ecde41f…f54d
0x34b655…2a6f
2 touches
0 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
2 touches
0 conflicts
0x22e559cc…383a
0x34b655…2a6f
2 touches
0 conflicts
0x23778a1f…dec4
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
0xae9018679a…898085
Audit this contract →
← previous block
·
next block →
recent activity