pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#72,287,857
← previous block
next block →
recent activity
Analyzing
Block #72,287,857
7 transactions · 6 stateful · 2026-05-04 02:39:40 UTC
Parallelism
71
/100
Blocked
17
%
Avg conflicts / tx
0.14
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#72,287,857
· 7 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
swapWithMagpieSignature
· blocks 1
#2
updateDataFeedsValuesPartial
#3
0x0f6795d9
#5
0x0f6795d9
#6
setData
#4
0x3f5c179b
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
0xd21679da…82e9
0x065c9d…c394
3 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
0x36d06497…c2f3
0x065c9d…c394
2 touches
0 conflicts
0xba0fe99d…9243
0x065c9d…c394
2 touches
0 conflicts
0xf41a73cc…440d
0x065c9d…c394
2 touches
0 conflicts
0xfc01eef2…0aa4
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
0xd21679dae8…ed82e9
Audit this contract →
← previous block
·
next block →
recent activity