pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#72,572,560
← previous block
next block →
recent activity
Analyzing
Block #72,572,560
6 transactions · 6 stateful · 2026-05-05 10:16:22 UTC
Parallelism
67
/100
Blocked
17
%
Avg conflicts / tx
0.17
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#72,572,560
· 6 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x9036287a
· blocks 1
#3
forward
#4
updateDataFeedsValuesPartial
#5
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
0x45c2059a…4160
0x065c9d…c394
4 touches
1 conflict
0xe773bd22…b610
0x065c9d…c394
4 touches
1 conflict
0x9fd05432…4b40
0x065c9d…c394
3 touches
1 conflict
0xd8e1814b…98a6
0x065c9d…c394
3 touches
1 conflict
0x7a51f48e…65de
0x065c9d…c394
3 touches
1 conflict
0xbbee74c2…567a
0x065c9d…c394
2 touches
0 conflicts
0xe2015259…3a0b
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