pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#87,050,033
← previous block
next block →
recent activity
Analyzing
Block #87,050,033
10 transactions · 9 stateful · 2026-07-11 12:01:58 UTC
Parallelism
80
/100
Blocked
11
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#87,050,033
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
0x5a5d9a99
#3
updateDataFeedsValuesPartial
#4
0x0f6795d9
· blocks 1
#5
0x0f6795d9
#6
setData
#8
0xed82b078
#9
0x6a52312e
#7
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfe0c34c7…76b1
0x34b655…2a6f
4 touches
1 conflict
0x8e5aabea…bec2
0x34b655…2a6f
4 touches
1 conflict
0xa020506f…7c60
0x34b655…2a6f
4 touches
1 conflict
0xa2e89145…7dfa
0x34b655…2a6f
4 touches
1 conflict
0xa6414776…aa49
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xec80a4ec…ed7a
0x34b655…2a6f
4 touches
1 conflict
0xfe0c34c7…76b0
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
1 conflict on slot
0xfe0c34c704…9f76b1
Audit this contract →
← previous block
·
next block →
recent activity