pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#71,741,897
← previous block
next block →
recent activity
Analyzing
Block #71,741,897
11 transactions · 6 stateful · 2026-05-01 13:57:22 UTC
Parallelism
82
/100
Blocked
17
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#71,741,897
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
updatePrices
#3
updatePrices
#4
updatePrices
#5
0xeffdedb0
#6
0x0c7abd22
· blocks 1
#7
updateDataFeedsValuesPartial
#9
setData
#10
executeOrders
#8
0x3f5c179b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x09f690e3…4298
0x065c9d…c394
4 touches
1 conflict
0x3766118b…9431
0x065c9d…c394
3 touches
1 conflict
0x0aaee5aa…0940
0x065c9d…c394
3 touches
1 conflict
0xc1d240ef…ef41
0x065c9d…c394
3 touches
1 conflict
0x5bf0ad95…2494
0x065c9d…c394
3 touches
1 conflict
0x33024094…9e4c
0x065c9d…c394
3 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
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
0x0000000000…00003d
Audit this contract →
← previous block
·
next block →
recent activity