pev
.
One block, wave by wave
→
offline
by Silk Nodes →
pev
/
block
/
#72,224,834
← previous block
next block →
recent activity
Analyzing
Block #72,224,834
13 transactions · 12 stateful · 2026-05-03 19:36:01 UTC
Parallelism
85
/100
Blocked
17
%
Avg conflicts / tx
0.15
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#72,224,834
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#3
transfer
#4
0xa96df62f
#5
0x9036287a
· blocks 1
#6
0x69f7a418
#7
0x98717539
#8
updateDataFeedsValuesPartial
#9
updateDataFeedsValuesPartial
#11
setData
#12
0x39435dac
#2
0x0c7abd22
#10
0x3f5c179b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
5
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7d2b0df5…c45f
0x065c9d…c394
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x35801c67…bcc5
0x1b6862…e19c
4 touches
1 conflict
0x41755291…977f
0x065c9d…c394
4 touches
1 conflict
0x47b807a2…3307
0x065c9d…c394
4 touches
1 conflict
0x8489440e…23e0
0xd32edf…ff58
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
0x7d2b0df5be…99c45f
Audit this contract →
← previous block
·
next block →
recent activity