pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#72,571,293
← previous block
next block →
recent activity
Analyzing
Block #72,571,293
8 transactions · 7 stateful · 2026-05-05 10:07:55 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,571,293
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#3
modifyLiquidities
#4
updateDataFeedsValuesPartial
#5
updateDataFeedsValuesPartial
#6
0x69f9c1f3
#7
setData
#2
0x3f5c179b
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
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x2c96b35a…c63d
0x065c9d…c394
2 touches
0 conflicts
0x5d53e848…2267
0x065c9d…c394
2 touches
0 conflicts
0x897b34fc…f9a1
0x065c9d…c394
2 touches
0 conflicts
0xa2f35c54…a891
0x065c9d…c394
2 touches
0 conflicts
0xa68d0ac3…a4eb
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:
0x065c9d28…a9c394
1 conflict on slot
0x0000000000…00003d
Audit this contract →
← previous block
·
next block →
recent activity