pev
.
One block, wave by wave
→
offline
by Silk Nodes →
pev
/
block
/
#71,243,573
← previous block
next block →
recent activity
Analyzing
Block #71,243,573
13 transactions · 8 stateful · 2026-04-29 06:34:26 UTC
Parallelism
85
/100
Blocked
13
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#71,243,573
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
· blocks 1
#3
updatePrices
#4
updatePrices
#5
0xe48910…f8f0
#6
0x6463ffd1
#7
updateDataFeedsValuesPartial
#8
setData
#9
forward
#10
forward
#11
0x69f1a6e9
#12
0x785f5745
#2
updatePrices
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xb857c1…9be1
4 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
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x2dc6d66e…08f6
0x065c9d…c394
2 touches
0 conflicts
0xca7a2ab6…e3b3
0x065c9d…c394
2 touches
0 conflicts
0xcd53e2c7…fe6e
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:
0xb857c13a…1a9be1
1 conflict on slot
0x0000000000…000002
Audit this contract →
← previous block
·
next block →
recent activity