pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#80,511,278
← previous block
next block →
recent activity
Analyzing
Block #80,511,278
10 transactions · 7 stateful · 2026-06-11 04:56:33 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
#80,511,278
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5339c59f
#2
0x5339c59f
#3
0xab083028
· blocks 1
#4
updateDataFeedsValuesPartial
#5
updateDataFeedsValuesPartial
#6
setData
#8
0x3f5c179b
#9
0xa78517…99bb
#7
0x3f5c179b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x52d65d97…1c96
0xa6afd3…d132
4 touches
1 conflict
0x9e20cccf…19cc
0xa6afd3…d132
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x160f117d…8e90
0x065c9d…c394
2 touches
0 conflicts
0x543370ce…37f3
0x065c9d…c394
2 touches
0 conflicts
0xbdc6f256…2d9c
0x065c9d…c394
2 touches
0 conflicts
0x046a928e…0012
0x2a68ba…90c5
2 touches
0 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
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
0x52d65d97d4…d01c96
Audit this contract →
← previous block
·
next block →
recent activity