pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#72,296,587
← previous block
next block →
recent activity
Analyzing
Block #72,296,587
9 transactions · 7 stateful · 2026-05-04 03:38:13 UTC
Parallelism
78
/100
Blocked
14
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#72,296,587
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5bf9264c
#2
0x5bf9264c
#3
0x0c7abd22
· blocks 1
#4
updateDataFeedsValuesPartial
#6
setData
#7
0x69f8151d
#8
0x39435dac
#5
0x3f5c179b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfb04ece8…fe80
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x22473194…66f7
0x065c9d…c394
4 touches
1 conflict
0x5c2aede2…3e1d
0x065c9d…c394
3 touches
1 conflict
0xc08546c7…75f6
0x065c9d…c394
3 touches
1 conflict
0xc740f774…d87c
0x065c9d…c394
3 touches
1 conflict
0x1709780a…f27b
0x065c9d…c394
3 touches
1 conflict
0xa2a78c06…344a
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
0xfb04ece8ae…c5fe80
Audit this contract →
← previous block
·
next block →
recent activity