pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#76,465,355
← previous block
next block →
recent activity
Analyzing
Block #76,465,355
10 transactions · 7 stateful · 2026-05-23 11:09:10 UTC
Parallelism
70
/100
Blocked
29
%
Avg conflicts / tx
0.3
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#76,465,355
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0xed82b078
· blocks 2
#3
updateDataFeedsValuesPartial
#4
0x98717539
#5
setData
#6
execute
#7
withdraw
#8
redeemDelegations
#2
0xab083028
· blocks 1
#9
0x0c7abd22
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
9
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcc8faac2…c766
0x065c9d…c394
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x18cf3003…51d1
0x065c9d…c394
2 touches
0 conflicts
0x06e40499…165e
0x1d1325…2305
2 touches
0 conflicts
0x14d15259…7553
0x1d1325…2305
2 touches
0 conflicts
0x1f5a2e2b…65f1
0x1d1325…2305
2 touches
0 conflicts
0x8488f10f…9353
0x1d1325…2305
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
3 conflicts on slot
0xcc8faac238…88c766
Audit this contract →
← previous block
·
next block →
recent activity