pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#72,575,478
← previous block
next block →
recent activity
Analyzing
Block #72,575,478
8 transactions · 7 stateful · 2026-05-05 10:35:49 UTC
Parallelism
75
/100
Blocked
14
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#72,575,478
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xed82b078
#2
updatePrices
· blocks 1
#4
0x3f5c179b
#5
updateDataFeedsValuesPartial
#6
0x69f9c87d
#7
setData
#3
updatePrices
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x7e9d3a…9fda
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x2008db35…1456
0x065c9d…c394
2 touches
0 conflicts
0x24968e6d…0132
0x065c9d…c394
2 touches
0 conflicts
0x760f8e84…496c
0x065c9d…c394
2 touches
0 conflicts
0x9a3fd26c…03f7
0x065c9d…c394
2 touches
0 conflicts
0xefd93c68…58bf
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:
0x7e9d3a8a…4f9fda
1 conflict on slot
0x0000000000…000002
Audit this contract →
← previous block
·
next block →
recent activity