pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#73,869,122
← previous block
next block →
recent activity
Analyzing
Block #73,869,122
10 transactions · 7 stateful · 2026-05-11 10:24:00 UTC
Parallelism
80
/100
Blocked
14
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,869,122
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
mint
· blocks 1
#3
0x6a01aeb8
#4
0x000000b2
#5
updateDataFeedsValuesPartial
#6
0xa09e9040
#7
setData
#8
updatePriceFeedsIfNecessary
#9
mint
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0007
0x1414f3…5137
4 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
0x084f249a…8b0e
0x065c9d…c394
2 touches
0 conflicts
0x593be5d5…b56b
0x065c9d…c394
2 touches
0 conflicts
0xa51f1267…9a1e
0x065c9d…c394
2 touches
0 conflicts
0xa5feb1d4…9b9a
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:
0x1414f3ba…045137
1 conflict on slot
0x0000000000…000007
Audit this contract →
← previous block
·
next block →
recent activity