pev
.
One block, wave by wave
→
offline
by Silk Nodes →
pev
/
block
/
#71,244,031
← previous block
next block →
recent activity
Analyzing
Block #71,244,031
13 transactions · 13 stateful · 2026-04-29 06:37:29 UTC
Parallelism
85
/100
Blocked
23
%
Avg conflicts / tx
0.23
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#71,244,031
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
trade
#2
updatePrices
· blocks 1
#4
0x98717539
· blocks 1
#5
0x6463ffd1
· blocks 1
#7
updateDataFeedsValuesPartial
#8
approve
#9
setData
#11
updatePrices
#12
updatePrices
#3
updatePrices
#6
0x6463ffd1
#10
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
4
w0
5
w0
6
w1
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xb857c1…9be1
4 touches
1 conflict
0x1c389468…6b0e
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x00000000…0004
0xd0f8a6…badc
4 touches
1 conflict
0x440b62c1…4200
0x065c9d…c394
3 touches
1 conflict
0xe0007579…2f9f
0x065c9d…c394
3 touches
1 conflict
0x09000000…0001
0x000000…1000
2 touches
0 conflicts
0x09000000…0007
0x000000…1000
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