pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#76,526,470
← previous block
next block →
recent activity
Analyzing
Block #76,526,470
12 transactions · 10 stateful · 2026-05-23 17:56:09 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
#76,526,470
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
0xab083028
· blocks 1
#3
0x5339c59f
#5
0x5339c59f
#6
0x5339c59f
#7
redeemDelegations
#8
setData
#9
0x0f6795d9
#10
0x0f6795d9
#11
0x39435dac
#4
0x5339c59f
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x77ed432f…fa04
0x065c9d…c394
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x95523e2a…4c01
0x065c9d…c394
2 touches
0 conflicts
0xa30caf1a…3ea0
0x065c9d…c394
2 touches
0 conflicts
0xc4101319…1dfc
0x065c9d…c394
2 touches
0 conflicts
0xd5bd7b19…d994
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
0x77ed432f03…d6fa04
Audit this contract →
← previous block
·
next block →
recent activity