pev
.
One block, wave by wave
→
offline
by Silk Nodes →
pev
/
block
/
#72,213,458
← previous block
next block →
recent activity
Analyzing
Block #72,213,458
11 transactions · 11 stateful · 2026-05-03 18:19:40 UTC
Parallelism
82
/100
Blocked
18
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#72,213,458
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
0x575c0012
#3
0x69f79234
#4
0x9036287a
· blocks 2
#5
updatePrices
#6
updateDataFeedsValuesPartial
#7
setData
#10
0x39435dac
#8
0x3f5c179b
#9
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
8
w1
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x41755291…977f
0x065c9d…c394
4 touches
1 conflict
0x47b807a2…3307
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xce661e66…c2be
0x065c9d…c394
3 touches
1 conflict
0x0edf19d4…273e
0x065c9d…c394
3 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…001f
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…002f
0x1b6862…e19c
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
0x4175529119…79977f
Audit this contract →
← previous block
·
next block →
recent activity