pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#87,668,843
← previous block
next block →
recent activity
Analyzing
Block #87,668,843
11 transactions · 6 stateful · 2026-07-14 09:00:39 UTC
Parallelism
82
/100
Blocked
17
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#87,668,843
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0f6795d9
· blocks 1
#2
updateDataFeedsValuesPartial
#4
setData
#5
0x2220e9…caec
#6
0xc8ab90…bf55
#7
0x4173d1…b80f
#8
0x148302…1cfa
#9
0xec347f…59ca
#10
0x39435dac
#3
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x337f8029…d9cc
0x34b655…2a6f
2 touches
0 conflicts
0x42d862e4…968d
0x34b655…2a6f
2 touches
0 conflicts
0x4943ce42…cab3
0x34b655…2a6f
2 touches
0 conflicts
0x7dea17f7…e870
0x34b655…2a6f
2 touches
0 conflicts
0x87d73281…b91b
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
0x0733be30d6…38112f
Audit this contract →
← previous block
·
next block →
recent activity