pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#72,979,215
← previous block
next block →
recent activity
Analyzing
Block #72,979,215
10 transactions · 7 stateful · 2026-05-07 07:26:10 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
#72,979,215
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x69fc3f0a
· blocks 1
#3
0x69fc3f0a
#4
fulfillWithERC20
#5
modifyLiquidities
#6
0x6df9e92b
#7
updateDataFeedsValuesPartial
#8
0xeffdedb0
#9
setData
#2
0x69fc3f0a
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x92339d95…0800
0x0000a8…8888
2 touches
0 conflicts
0x40e5ea25…2042
0x188d58…ea8e
2 touches
0 conflicts
0x9b7d6767…4f58
0x188d58…ea8e
2 touches
0 conflicts
0x9b7d6767…4f5a
0x188d58…ea8e
2 touches
0 conflicts
0xab99c64e…5937
0x188d58…ea8e
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:
0x681e908b…e1ae09
1 conflict on slot
0x0d622e34f9…000000
Audit this contract →
← previous block
·
next block →
recent activity