pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#76,232,214
← previous block
next block →
recent activity
Analyzing
Block #76,232,214
13 transactions · 11 stateful · 2026-05-22 09:17:07 UTC
Parallelism
85
/100
Blocked
18
%
Avg conflicts / tx
0.15
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#76,232,214
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
exactInput
#2
execute
#3
updatePrices
· blocks 1
#5
0x5bf9264c
#6
0x98717539
· blocks 1
#8
updateDataFeedsValuesPartial
#9
0xb463e9…f83b
#10
executeBatch
#11
setData
#12
0x7d8f06…a442
#4
updatePrices
#7
0x98717539
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
6
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0002
0xab3526…fa38
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x12309510…0ac2
0x000000…012a
2 touches
0 conflicts
0x33018431…8f5c
0x188d58…ea8e
2 touches
0 conflicts
0x33018431…8f5d
0x188d58…ea8e
2 touches
0 conflicts
0x22e0cc1d…ad04
0x34b655…2a6f
2 touches
0 conflicts
0x86cea35b…bdff
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
0x60f7fbaf90…97bd58
Audit this contract →
← previous block
·
next block →
recent activity