pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#76,140,653
← previous block
next block →
recent activity
Analyzing
Block #76,140,653
10 transactions · 8 stateful · 2026-05-21 23:07:06 UTC
Parallelism
80
/100
Blocked
13
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#76,140,653
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#2
updatePrices
#3
0x98717539
#5
updateDataFeedsValuesPartial
#6
0x0f6795d9
#7
0x0f6795d9
#8
0xed82b078
#9
setData
#4
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
4
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
0x339901df…93ea
0x065c9d…c394
2 touches
0 conflicts
0x4ff6bd1c…73b9
0x065c9d…c394
2 touches
0 conflicts
0x847d3d42…1338
0x065c9d…c394
2 touches
0 conflicts
0x9dc696c5…10af
0x065c9d…c394
2 touches
0 conflicts
0xa557c6bc…ba6f
0x065c9d…c394
2 touches
0 conflicts
0xfe2bac2b…2cec
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