pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#75,954,902
← previous block
next block →
recent activity
Analyzing
Block #75,954,902
11 transactions · 10 stateful · 2026-05-21 02:29:29 UTC
Parallelism
82
/100
Blocked
20
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#75,954,902
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xed82b078
· blocks 1
#3
updatePrices
· blocks 1
#5
redeemDelegations
#6
0x0f6795d9
#7
0x0f6795d9
#8
updateDataFeedsValuesPartial
#9
setData
#10
approve
#2
0xab083028
#4
updatePrices
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf79ae213…cf45
0xa6afd3…d132
4 touches
1 conflict
0xf9f153d3…a30c
0xa6afd3…d132
4 touches
1 conflict
0x00000000…0002
0xab3526…fa38
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0xd6cb443c…912d
0xa6afd3…d132
3 touches
1 conflict
0x3484c9df…bfd5
0x1d1325…2305
2 touches
0 conflicts
0x8cf3d245…1d0d
0x1d1325…2305
2 touches
0 conflicts
0xdb067026…9eb8
0x1d1325…2305
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:
0xa6afd386…b0d132
1 conflict on slot
0xf79ae213e8…becf45
Audit this contract →
← previous block
·
next block →
recent activity