pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#71,701,919
← previous block
next block →
recent activity
Analyzing
Block #71,701,919
12 transactions · 9 stateful · 2026-05-01 09:31:06 UTC
Parallelism
75
/100
Blocked
33
%
Avg conflicts / tx
0.33
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#71,701,919
· 12 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x0c7abd22
· blocks 2
#3
0x1094dc9f
#5
updatePrices
#6
0x5bf9264c
#7
updateDataFeedsValuesPartial
#8
0x5bf9264c
#9
0xeffdedb0
#11
setData
#2
0x0c7abd22
· blocks 2
#4
0x0c7abd22
#10
0x3f5c179b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
4
w2
10
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8ff8326d…7086
0xd32edf…ff58
5 touches
3 conflicts
0xba5743c7…21c3
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x92d610a6…9a40
0x2a68ba…90c5
4 touches
1 conflict
0x0551508c…2b05
0x065c9d…c394
3 touches
1 conflict
0x00000000…0002
0x7e9d3a…9fda
2 touches
0 conflicts
0x641245e3…6323
0xc8689a…ee79
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:
0xd32edf66…9fff58
3 conflicts on slot
0x8ff8326dfb…677086
Audit this contract →
← previous block
·
next block →
recent activity