pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#86,793,509
← previous block
next block →
recent activity
Analyzing
Block #86,793,509
12 transactions · 11 stateful · 2026-07-10 07:27:18 UTC
Parallelism
83
/100
Blocked
9
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,793,509
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
exactInput
#2
executePacked
#3
updatePrices
#4
0x62be7533
#5
updateDataFeedsValuesPartial
#6
0x0f6795d9
· blocks 1
#7
0x5339c59f
#9
setData
#10
0x39435dac
#11
0xc7e3ec2c
#8
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xebeee24a…ed8d
0x34b655…2a6f
4 touches
1 conflict
0x74550a4b…68bd
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4ab
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
2 touches
0 conflicts
0x06cdf7f0…fbe6
0x3bd359…433a
2 touches
0 conflicts
0xb9eb1318…ce53
0x3bd359…433a
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
0xebeee24aff…40ed8d
Audit this contract →
← previous block
·
next block →
recent activity