pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#72,571,080
← previous block
next block →
recent activity
Analyzing
Block #72,571,080
10 transactions · 10 stateful · 2026-05-05 10:06:31 UTC
Parallelism
70
/100
Blocked
20
%
Avg conflicts / tx
0.2
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#72,571,080
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#3
_makeSwaps
#4
updatePrices
#5
0x98717539
#6
updateDataFeedsValuesPartial
#8
setData
#9
0x39435dac
#2
0x0c7abd22
· blocks 1
#7
0x3f5c179b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
7
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x2fe11b27…d951
0xd32edf…ff58
3 touches
1 conflict
0x00000000…0003
0x0594c7…a3be
2 touches
0 conflicts
0x00000000…0004
0x0594c7…a3be
2 touches
0 conflicts
0x00000000…0005
0x0594c7…a3be
2 touches
0 conflicts
0x7a079794…fc3b
0x0594c7…a3be
2 touches
0 conflicts
0xa5d3ee6e…8583
0x0594c7…a3be
2 touches
0 conflicts
0x95b2bb34…cb82
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