pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#76,024,092
← previous block
next block →
recent activity
Analyzing
Block #76,024,092
8 transactions · 7 stateful · 2026-05-21 10:10:10 UTC
Parallelism
75
/100
Blocked
14
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#76,024,092
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
0xed82b078
· blocks 1
#3
0xec2bd3f2
#4
setData
#5
claimRewards
#7
0xbf82f22b
#6
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x13d36630…179e
0x065c9d…c394
4 touches
1 conflict
0x3bb7fc92…a85c
0x065c9d…c394
3 touches
1 conflict
0x33da1c7d…4ff5
0x065c9d…c394
3 touches
1 conflict
0x0b000000…0001
0x000000…1000
2 touches
0 conflicts
0x443a3e47…f4a4
0x065c9d…c394
2 touches
0 conflicts
0xad436fd9…33fd
0x065c9d…c394
2 touches
0 conflicts
0x00000000…0000
0x120151…c1d6
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