pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#86,914,538
← previous block
next block →
recent activity
Analyzing
Block #86,914,538
10 transactions · 9 stateful · 2026-07-10 20:56:35 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
#86,914,538
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
updatePrices
#3
updateDataFeedsValuesPartial
#4
0x0f6795d9
#5
0x0f6795d9
· blocks 1
#6
setData
#7
0x3f5c179b
#8
forward
#9
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8d6062bd…88e0
0x34b655…2a6f
4 touches
1 conflict
0xb678410a…0edb
0x34b655…2a6f
4 touches
1 conflict
0x6083af24…a0df
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0002
0x04fdea…47d7
2 touches
0 conflicts
0x00000000…00c9
0x34b655…2a6f
2 touches
0 conflicts
0x007b42ba…13dc
0x34b655…2a6f
2 touches
0 conflicts
0x050376db…0f47
0x34b655…2a6f
2 touches
0 conflicts
0x09a0ee1a…3102
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
0x8d6062bdd8…c188e0
Audit this contract →
← previous block
·
next block →
recent activity