pev
.
One block, wave by wave
→
offline
by Silk Nodes →
pev
/
block
/
#71,560,599
← previous block
next block →
recent activity
Analyzing
Block #71,560,599
11 transactions · 9 stateful · 2026-04-30 17:50:33 UTC
Parallelism
73
/100
Blocked
22
%
Avg conflicts / tx
0.27
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#71,560,599
· 11 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0xed82b078
· blocks 2
#2
0x69f396e1
#3
updateDataFeedsValuesPartial
#4
updateDataFeedsValuesPartial
#5
0xeffdedb0
#7
setData
#8
0x0c7abd22
#10
0x69f396e1
#6
0xf2acfec3
· blocks 1
#9
0x3f5c179b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
6
w1
9
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x38a9a856…b1f3
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xb0b2d669…4f40
0x065c9d…c394
3 touches
1 conflict
0x09000000…0001
0x000000…1000
2 touches
0 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x766ac8e3…25c9
0x065c9d…c394
2 touches
0 conflicts
0x438cf5f6…f077
0x2a68ba…90c5
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
0x38a9a856b5…10b1f3
Audit this contract →
← previous block
·
next block →
recent activity