pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#72,283,517
← previous block
next block →
recent activity
Analyzing
Block #72,283,517
10 transactions · 10 stateful · 2026-05-04 02:10:27 UTC
Parallelism
80
/100
Blocked
20
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#72,283,517
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x9036287a
· blocks 1
#2
0x69f8008a
#3
updateDataFeedsValuesPartial
#4
updateDataFeedsValuesPartial
#6
0x0c7abd22
#7
setData
#8
0xc2d867a5
· blocks 1
#5
0x3f5c179b
#9
0xc2d867a5
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
5
w1
8
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x33018431…8f5d
0x188d58…ea8e
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x00000000…0004
0x465a0b…3980
4 touches
1 conflict
0x00000000…0005
0x465a0b…3980
4 touches
1 conflict
0xc9c1648c…bea4
0x465a0b…3980
4 touches
1 conflict
0x17606ba6…1b6e
0x754704…b603
4 touches
1 conflict
0xb0f4dbcb…926a
0x754704…b603
4 touches
1 conflict
0x12309510…0ac2
0x000000…012a
4 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:
0x188d586d…f9ea8e
1 conflict on slot
0x330184318b…418f5d
Audit this contract →
← previous block
·
next block →
recent activity