pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#85,940,458
← previous block
next block →
recent activity
Analyzing
Block #85,940,458
12 transactions · 10 stateful · 2026-07-06 08:27:01 UTC
Parallelism
83
/100
Blocked
10
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,940,458
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0f6795d9
· blocks 1
#2
0x0f6795d9
#3
verifyOracleProofV2
#4
0xed82b078
#5
relay
#7
updateDataFeedsValuesPartial
#8
0x6a4b674d
#9
0xd708c5d8
#10
setData
#11
0x39435dac
#6
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xafd867b7…2b2e
0x34b655…2a6f
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
0x29caf66d…5617
0x065c9d…c394
2 touches
0 conflicts
0x9ebbb66a…8232
0x065c9d…c394
2 touches
0 conflicts
0x00000000…009a
0x16f70c…c3dd
2 touches
0 conflicts
0x72a152dd…a078
0x16f70c…c3dd
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
0xafd867b7ed…d92b2e
Audit this contract →
← previous block
·
next block →
recent activity