pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#72,993,938
← previous block
next block →
recent activity
Analyzing
Block #72,993,938
12 transactions · 10 stateful · 2026-05-07 09:04:21 UTC
Parallelism
83
/100
Blocked
20
%
Avg conflicts / tx
0.17
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#72,993,938
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x121eab2f
· blocks 1
#2
0x5bf9264c
#3
0x5bf9264c
#4
0x98717539
· blocks 1
#5
forward
#6
updateDataFeedsValuesPartial
#7
updateDataFeedsValuesPartial
#9
0xeffdedb0
#10
setData
#8
0x5339c59f
#11
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
4
w0
8
w1
11
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0b390c61…dc07
0x065c9d…c394
4 touches
1 conflict
0x47c1a8e8…f74a
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x4e509abe…856d
0x065c9d…c394
2 touches
0 conflicts
0x8774871f…8cee
0x065c9d…c394
2 touches
0 conflicts
0xa9735a87…15bf
0x065c9d…c394
2 touches
0 conflicts
0xbd7e37a9…9eb5
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
0x0b390c6160…02dc07
Audit this contract →
← previous block
·
next block →
recent activity