pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#76,387,850
← previous block
next block →
recent activity
Analyzing
Block #76,387,850
10 transactions · 8 stateful · 2026-05-23 02:33:41 UTC
Parallelism
80
/100
Blocked
25
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#76,387,850
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
0xed82b078
· blocks 1
#3
0xa96df62f
#4
0xed82b078
#5
updateDataFeedsValuesPartial
#7
setData
#8
0x39435dac
· blocks 1
#6
0xed82b078
#9
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
6
w1
8
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc51d3663…0f45
0xa6afd3…d132
4 touches
1 conflict
0x53b4ef2b…8a05
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x4b58369f…5e20
0xa6afd3…d132
4 touches
1 conflict
0xabdbd5ed…73e4
0xa6afd3…d132
3 touches
1 conflict
0xbd01a8c1…9c36
0xa6afd3…d132
3 touches
1 conflict
0x00000000…001a
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…002a
0x1b6862…e19c
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
0xc51d366315…ef0f45
Audit this contract →
← previous block
·
next block →
recent activity