pev
.
One block, wave by wave
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#76,242,456
← previous block
next block →
recent activity
Analyzing
Block #76,242,456
7 transactions · 6 stateful · 2026-05-22 10:25:16 UTC
Parallelism
71
/100
Blocked
17
%
Avg conflicts / tx
0.14
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#76,242,456
· 7 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
updateDataFeedsValuesPartial
#3
redeemDelegations
· blocks 1
#5
setData
#6
0x39435dac
#4
redeemDelegations
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0000
0xe661d8…c710
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x13c6a583…0bf3
0x065c9d…c394
2 touches
0 conflicts
0x1d2ca791…8679
0x065c9d…c394
2 touches
0 conflicts
0x1f3b37cb…357f
0x065c9d…c394
2 touches
0 conflicts
0x4249cee5…efb5
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:
0xe661d843…4ac710
1 conflict on slot
0x0000000000…000000
Audit this contract →
← previous block
·
next block →
recent activity