pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#72,977,961
← previous block
next block →
recent activity
Analyzing
Block #72,977,961
11 transactions · 8 stateful · 2026-05-07 07:17:51 UTC
Parallelism
82
/100
Blocked
13
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#72,977,961
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
exactInputSingle
#2
0x1be2fb9c
#3
0x0c7abd22
· blocks 1
#4
0x1be2fb9c
#5
updateDataFeedsValuesPartial
#6
updateDataFeedsValuesPartial
#8
createModule
#9
0xeffdedb0
#10
setData
#7
0x0c7abd22
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x04fd0503…5951
0xd32edf…ff58
3 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0xb1632c2f…d991
0x0a3323…0a3c
2 touches
0 conflicts
0xdeaab6a3…ccad
0x0a3323…0a3c
2 touches
0 conflicts
0x558f6d0c…d50f
0x3bd359…433a
2 touches
0 conflicts
0x63f5c02f…6853
0x3bd359…433a
2 touches
0 conflicts
0x00000000…0000
0x850662…52d0
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:
0xd32edf66…9fff58
1 conflict on slot
0x04fd050387…205951
Audit this contract →
← previous block
·
next block →
recent activity