pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#74,458,333
← previous block
next block →
recent activity
Analyzing
Block #74,458,333
11 transactions · 8 stateful · 2026-05-14 03:47:00 UTC
Parallelism
82
/100
Blocked
13
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,458,333
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#2
updatePrices
#3
updateDataFeedsValuesPartial
#4
updateDataFeedsValuesPartial
#5
0x98717539
#6
0x5339c59f
#8
setData
#9
0x74bfc4…ff47
#10
0x39435dac
#7
0x5339c59f
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x80629aca…a1a1
0x065c9d…c394
4 touches
1 conflict
0x35719f7d…0c09
0x065c9d…c394
3 touches
1 conflict
0x310b755f…05bc
0x065c9d…c394
3 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x54446f7e…c5ca
0x065c9d…c394
2 touches
0 conflicts
0xa37d962b…c55b
0x065c9d…c394
2 touches
0 conflicts
0xc998adb0…35d7
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
0x80629aca17…94a1a1
Audit this contract →
← previous block
·
next block →
recent activity