pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#86,814,309
← previous block
next block →
recent activity
Analyzing
Block #86,814,309
13 transactions · 13 stateful · 2026-07-10 09:46:17 UTC
Parallelism
85
/100
Blocked
8
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,814,309
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
exactOutputSingle
#3
0xab083028
#4
updatePrices
#5
updateDataFeedsValuesPartial
#6
updateDataFeedsValuesPartial
#7
forward
#8
0x0f6795d9
#9
0x0f6795d9
#10
0x6a50bfe0
· blocks 1
#12
setData
#11
0x6a50bfe0
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
10
w0
11
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x167a2a69…65a0
0x065c9d…c394
2 touches
0 conflicts
0x23a069d1…20c4
0x065c9d…c394
2 touches
0 conflicts
0x7d73f802…840d
0x065c9d…c394
2 touches
0 conflicts
0x870e41b2…d7f4
0x065c9d…c394
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:
0x681e908b…e1ae09
1 conflict on slot
0x0d622e34f9…000000
Audit this contract →
← previous block
·
next block →
recent activity