pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#73,214,450
← previous block
next block →
recent activity
Analyzing
Block #73,214,450
12 transactions · 10 stateful · 2026-05-08 09:31:24 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
#73,214,450
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#2
updatePrices
· blocks 1
#4
0x5bf9264c
#5
0x5bf9264c
#6
0x121eab2f
#7
0x98717539
#8
updateDataFeedsValuesPartial
#9
setData
#11
0xeffdedb0
#3
updatePrices
#10
0x5339c59f
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w0
3
w1
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc79bcebd…b12e
0x065c9d…c394
4 touches
1 conflict
0x00000000…0002
0xab3526…fa38
4 touches
1 conflict
0x093f81cc…cc0b
0x065c9d…c394
3 touches
1 conflict
0xec5be2e3…17f7
0x065c9d…c394
3 touches
1 conflict
0x49495547…ae5f
0x065c9d…c394
2 touches
0 conflicts
0x5ea44d90…ae7b
0x065c9d…c394
2 touches
0 conflicts
0xbd7e37a9…9eb5
0x065c9d…c394
2 touches
0 conflicts
0x00000000…0012
0x1b6862…e19c
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
0xc79bcebd49…bcb12e
Audit this contract →
← previous block
·
next block →
recent activity