pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#80,482,238
← previous block
next block →
recent activity
Analyzing
Block #80,482,238
12 transactions · 10 stateful · 2026-06-11 01:43:12 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
#80,482,238
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xed82b078
· blocks 1
#3
0xed82b078
#4
updateDataFeedsValuesPartial
#5
updateDataFeedsValuesPartial
#6
verifyOracleProofV2
#7
forward
#8
transfer
#9
0xe9316489
#10
setData
#11
execOrders
#2
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0be2e0c0…d452
0x065c9d…c394
2 touches
0 conflicts
0x23a61682…e537
0x065c9d…c394
2 touches
0 conflicts
0x2df5f387…67e7
0x065c9d…c394
2 touches
0 conflicts
0xd4206383…6a7b
0x065c9d…c394
2 touches
0 conflicts
0x262bb27b…6b2c
0x11ed3b…2c96
2 touches
0 conflicts
0x00000000…009a
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:
Kuru Exchange: Market-MON/USDC
1 conflict on slot
0x0000000000…00003d
Audit this contract →
← previous block
·
next block →
recent activity