pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#85,213,968
← previous block
next block →
recent activity
Analyzing
Block #85,213,968
10 transactions · 9 stateful · 2026-07-02 23:47:28 UTC
Parallelism
80
/100
Blocked
11
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,213,968
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
updatePrices
#3
0x39435dac
· blocks 1
#4
updateDataFeedsValuesPartial
#5
0x0f6795d9
#6
0x6a46f908
#7
setData
#9
0xc7e3ec2c
#8
redeemDelegations
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7edd2906…e6fd
0x34b655…2a6f
4 touches
1 conflict
0xec0e0220…cb90
0x34b655…2a6f
4 touches
1 conflict
0x4755fafb…859b
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0002
0x04fdea…47d7
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x00c45c58…7df2
0x34b655…2a6f
2 touches
0 conflicts
0x03a55247…abfe
0x34b655…2a6f
2 touches
0 conflicts
0x0b17ce05…ab72
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
0x7edd290610…94e6fd
Audit this contract →
← previous block
·
next block →
recent activity