pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#85,176,173
← previous block
next block →
recent activity
Analyzing
Block #85,176,173
10 transactions · 10 stateful · 2026-07-02 19:35:46 UTC
Parallelism
80
/100
Blocked
20
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,176,173
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
· blocks 1
#2
updatePrices
#3
0x5a5d9a99
· blocks 1
#4
updateDataFeedsValuesPartial
#7
setData
#8
0x6a46be09
#9
0x39435dac
#5
0x3f5c179b
#6
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w0
5
w1
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x85631114…3ff6
0xa6afd3…d132
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x987aeb55…0e2a
0xa6afd3…d132
4 touches
1 conflict
0x765cd07a…1018
0x34b655…2a6f
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
2 touches
0 conflicts
0xef65bff3…7c9d
0x2a68ba…90c5
2 touches
0 conflicts
0x1853f465…3255
0x34b655…2a6f
2 touches
0 conflicts
0x2b268fa9…eba2
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:
Kuru Exchange: Market-WETH/USDC
1 conflict on slot
0x8563111480…873ff6
Audit this contract →
← previous block
·
next block →
recent activity