pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#76,148,613
← previous block
next block →
recent activity
Analyzing
Block #76,148,613
12 transactions · 8 stateful · 2026-05-22 00:00:12 UTC
Parallelism
83
/100
Blocked
13
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#76,148,613
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x39ecce49
#2
0x719d975a
#3
0xed82b078
· blocks 1
#4
0x6c05cd2b
#5
updateDataFeedsValuesPartial
#7
0x62be7533
#8
0xc5918880
#9
0xaf47a8bb
#10
0xc5a04723
#11
setData
#6
0x0c7abd22
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf85c75bc…00b5
0xa6afd3…d132
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…0000
0x116e7d…d8f1
2 touches
0 conflicts
0x00000000…0002
0x116e7d…d8f1
2 touches
0 conflicts
0x00000000…0003
0x116e7d…d8f1
2 touches
0 conflicts
0xc439a6eb…c510
0x188d58…ea8e
2 touches
0 conflicts
0xc439a6eb…c512
0x188d58…ea8e
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
0xf85c75bcf3…1f00b5
Audit this contract →
← previous block
·
next block →
recent activity