pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#72,855,848
← previous block
next block →
recent activity
Analyzing
Block #72,855,848
9 transactions · 8 stateful · 2026-05-06 17:45:07 UTC
Parallelism
78
/100
Blocked
13
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#72,855,848
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x121eab2f
· blocks 1
#2
updateDataFeedsValuesPartial
#3
updateDataFeedsValuesPartial
#4
setData
#6
forward
#7
0xeffdedb0
#8
0x39435dac
#5
0x0c7abd22
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x1a7848f5…12a2
0x065c9d…c394
4 touches
1 conflict
0xce7bfe5e…5e58
0x065c9d…c394
4 touches
1 conflict
0x8bcd90e8…5673
0x065c9d…c394
2 touches
0 conflicts
0xa63b62bd…bf50
0x065c9d…c394
2 touches
0 conflicts
0xffc5cd88…2870
0x065c9d…c394
2 touches
0 conflicts
0x70b2f813…783c
0x2a68ba…90c5
2 touches
0 conflicts
0xe09eda07…8dda
0x2a68ba…90c5
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