pev
.
One block, wave by wave
→
offline
by Silk Nodes →
pev
/
block
/
#71,557,642
← previous block
next block →
recent activity
Analyzing
Block #71,557,642
12 transactions · 10 stateful · 2026-04-30 17:30:48 UTC
Parallelism
83
/100
Blocked
10
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#71,557,642
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x54390b8b
#2
0x05ee6a22
#3
updatePrices
#4
0x69f3923f
#5
0x0c7abd22
· blocks 1
#6
updateDataFeedsValuesPartial
#7
0xeffdedb0
#8
0x69f3923f
#9
setData
#11
0x39435dac
#10
0x0c7abd22
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc7f96d76…ddcf
0xd32edf…ff58
3 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
0x63bb92d2…3dfd
0x065c9d…c394
2 touches
0 conflicts
0xfcb7b8b2…ebb3
0x065c9d…c394
2 touches
0 conflicts
0x438cf5f6…f077
0x2a68ba…90c5
2 touches
0 conflicts
0x75b2738b…c827
0x2a68ba…90c5
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:
0xd32edf66…9fff58
1 conflict on slot
0xc7f96d76ad…18ddcf
Audit this contract →
← previous block
·
next block →
recent activity