pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#86,679,756
← previous block
next block →
recent activity
Analyzing
Block #86,679,756
11 transactions · 7 stateful · 2026-07-09 18:47:40 UTC
Parallelism
82
/100
Blocked
14
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,679,756
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
updateDataFeedsValuesPartial
#3
updateDataFeedsValuesPartial
#4
0x0f6795d9
· blocks 1
#6
0x57368ddf
#7
0x0f6795d9
#8
setData
#9
0xcdc56f…1231
#10
0x39435dac
#5
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6184af9b…a93e
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0x36203b4b…8a05
0x34b655…2a6f
4 touches
1 conflict
0x36203b4b…8a06
0x34b655…2a6f
4 touches
1 conflict
0x273c2a35…7513
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xf23e15be…1749
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
0x6184af9bc9…01a93e
Audit this contract →
← previous block
·
next block →
recent activity