pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#76,089,927
← previous block
next block →
recent activity
Analyzing
Block #76,089,927
13 transactions · 10 stateful · 2026-05-21 17:29:15 UTC
Parallelism
85
/100
Blocked
20
%
Avg conflicts / tx
0.15
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#76,089,927
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
· blocks 2
#2
execute
#3
approve
#4
swap
#6
0x1a945f9c
#8
updateDataFeedsValuesPartial
#9
verifyOracleProofV2
#10
forward
#11
setData
#12
0x42dd8743
#5
0x0c7abd22
#7
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
5
w1
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x4cd24559…b9e0
0xd32edf…ff58
3 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x19dbd38f…6dcd
0x065c9d…c394
2 touches
0 conflicts
0x2191eff7…9543
0x065c9d…c394
2 touches
0 conflicts
0x515b3963…4331
0x065c9d…c394
2 touches
0 conflicts
0x5bb486d0…f4c2
0x065c9d…c394
2 touches
0 conflicts
0xada21f5b…e6c3
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:
Kuru Exchange: Market-MON/USDC
1 conflict on slot
0x0000000000…00003d
Audit this contract →
← previous block
·
next block →
recent activity