pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#76,445,094
← previous block
next block →
recent activity
Analyzing
Block #76,445,094
6 transactions · 5 stateful · 2026-05-23 08:54:20 UTC
Parallelism
50
/100
Blocked
40
%
Avg conflicts / tx
0.5
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#76,445,094
· 6 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
0x85367786
· blocks 2
#5
setData
#3
0x85367786
· blocks 1
#4
0x85367786
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
4
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x247d3d81…6084
0x2c4667…b389
6 touches
3 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x16431e32…cf31
0x2c4667…b389
2 touches
0 conflicts
0x3f8b41c7…98d6
0x2c4667…b389
2 touches
0 conflicts
0x648f6b39…43a4
0x2c4667…b389
2 touches
0 conflicts
0x01a89030…f786
0x368ee5…7ca4
2 touches
0 conflicts
0x5b571ba0…f13a
0x368ee5…7ca4
2 touches
0 conflicts
0x68faa0b9…14af
0x368ee5…7ca4
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:
0x2c466769…99b389
3 conflicts on slot
0x247d3d814d…366084
Audit this contract →
← previous block
·
next block →
recent activity