pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#75,732,067
← previous block
next block →
recent activity
Analyzing
Block #75,732,067
10 transactions · 7 stateful · 2026-05-20 01:44:20 UTC
Parallelism
80
/100
Blocked
14
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#75,732,067
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
transfer
#2
0x7864c218
#3
updateDataFeedsValuesPartial
#4
0x98717539
· blocks 1
#6
setData
#7
0x39abec6b
#8
0xaa0a9d…9db4
#9
0x01627e…da5c
#5
0x98717539
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x01ea5a68…e607
0x2ab50b…5c41
2 touches
0 conflicts
0x04077f86…d5fd
0x2ab50b…5c41
2 touches
0 conflicts
0x047d8971…c728
0x2ab50b…5c41
2 touches
0 conflicts
0x080c1dbe…ba16
0x2ab50b…5c41
2 touches
0 conflicts
0x0a5e8545…2c05
0x2ab50b…5c41
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:
Perpl
1 conflict on slot
0x60f7fbaf90…97bd58
Audit this contract →
← previous block
·
next block →
recent activity