pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#71,036,975
← previous block
next block →
recent activity
Analyzing
Block #71,036,975
8 transactions · 7 stateful · 2026-04-28 07:38:59 UTC
Parallelism
75
/100
Blocked
14
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#71,036,975
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
0x98717539
#3
updateDataFeedsValuesPartial
#4
0x6463ffd1
· blocks 1
#6
0x69f0648b
#7
setData
#5
0x6463ffd1
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3d0f8a93…dd8b
0x065c9d…c394
4 touches
1 conflict
0x6b47c88e…e0ff
0x065c9d…c394
4 touches
1 conflict
0x77c42667…dbc4
0x065c9d…c394
4 touches
1 conflict
0x87ece408…e446
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x00000000…0004
0xd0f8a6…badc
4 touches
1 conflict
0x2c653f98…6e5a
0x34b655…2a6f
2 touches
0 conflicts
0x3ff344f5…30bf
0x34b655…2a6f
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
0x3d0f8a9354…a5dd8b
Audit this contract →
← previous block
·
next block →
recent activity