pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#76,309,699
← previous block
next block →
recent activity
Analyzing
Block #76,309,699
10 transactions · 8 stateful · 2026-05-22 17:52:38 UTC
Parallelism
80
/100
Blocked
13
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#76,309,699
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
approve
· blocks 1
#3
0xab083028
#4
updateDataFeedsValuesPartial
#5
0x98717539
#6
0x98717539
#7
setData
#8
execute
#9
0x0f6795d9
#2
swap
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
0xad66f231…3c24
0xe6eddc…7777
2 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
0x7f83be6b…a549
0x065c9d…c394
2 touches
0 conflicts
0x84c16c32…19ee
0x065c9d…c394
2 touches
0 conflicts
0xa86d63c7…8102
0x065c9d…c394
2 touches
0 conflicts
0xfdfe5f77…a663
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:
0xe6eddc07…237777
1 conflict on slot
0xad66f23135…753c24
Audit this contract →
← previous block
·
next block →
recent activity