pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#72,572,373
← previous block
next block →
recent activity
Analyzing
Block #72,572,373
8 transactions · 7 stateful · 2026-05-05 10:15:07 UTC
Parallelism
75
/100
Blocked
29
%
Avg conflicts / tx
0.25
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#72,572,373
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
exactOutputSingle
#2
updatePrices
· blocks 1
#4
0x9036287a
· blocks 1
#5
updateDataFeedsValuesPartial
#7
setData
#3
updatePrices
#6
0x3f5c179b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
4
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd05865a4…98b0
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xad5f0940…e334
0x065c9d…c394
4 touches
1 conflict
0x00000000…0002
0x7e9d3a…9fda
4 touches
1 conflict
0xe7cb8a57…a88e
0x065c9d…c394
3 touches
1 conflict
0x27fa10a5…f0c2
0x065c9d…c394
3 touches
1 conflict
0xb98fef85…7d25
0x065c9d…c394
3 touches
1 conflict
0x0b015896…7c0c
0x065c9d…c394
3 touches
1 conflict
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:
0x065c9d28…a9c394
1 conflict on slot
0xd05865a416…9498b0
Audit this contract →
← previous block
·
next block →
recent activity