pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#72,429,436
← previous block
next block →
recent activity
Analyzing
Block #72,429,436
12 transactions · 11 stateful · 2026-05-04 18:23:20 UTC
Parallelism
83
/100
Blocked
18
%
Avg conflicts / tx
0.17
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#72,429,436
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x9036287a
· blocks 1
#2
0x69f8e48f
#3
0x1a945f9c
#4
0x98717539
· blocks 1
#5
updateDataFeedsValuesPartial
#7
0x0c7abd22
#8
0x96e62922
#9
forward
#10
setData
#6
0x3f5c179b
#11
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
4
w0
6
w1
11
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xadac4a86…c2bc
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x5c8c6ab6…dc36
0x065c9d…c394
2 touches
0 conflicts
0x92cecaf8…402f
0x065c9d…c394
2 touches
0 conflicts
0x94dd0368…8021
0x065c9d…c394
2 touches
0 conflicts
0xd2170ce1…84ac
0x065c9d…c394
2 touches
0 conflicts
0xe0e33513…1cab
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:
0x34b6552d…112a6f
1 conflict on slot
0xadac4a860c…a3c2bc
Audit this contract →
← previous block
·
next block →
recent activity