pev
.
One block, wave by wave
→
offline
by Silk Nodes →
pev
/
block
/
#71,746,397
← previous block
next block →
recent activity
Analyzing
Block #71,746,397
11 transactions · 10 stateful · 2026-05-01 14:27:24 UTC
Parallelism
73
/100
Blocked
20
%
Avg conflicts / tx
0.27
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#71,746,397
· 11 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
updatePrices
· blocks 2
#4
0x93933c…3125
#5
0xeffdedb0
#6
0x3f5c179b
#7
updateDataFeedsValuesPartial
#8
0xb0435a94
#9
setData
#10
0x39435dac
#2
updatePrices
· blocks 1
#3
updatePrices
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x7e9d3a…9fda
6 touches
3 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x92339d95…0800
0x0000a8…8888
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x0722ccc4…a09c
0x065c9d…c394
2 touches
0 conflicts
0x7b1772b8…f31f
0x065c9d…c394
2 touches
0 conflicts
0xa2945777…e466
0x065c9d…c394
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:
0x7e9d3a8a…4f9fda
3 conflicts on slot
0x0000000000…000002
Audit this contract →
← previous block
·
next block →
recent activity