pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#80,264,917
← previous block
next block →
recent activity
Analyzing
Block #80,264,917
9 transactions · 5 stateful · 2026-06-10 01:34:58 UTC
Parallelism
78
/100
Blocked
20
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#80,264,917
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
· blocks 1
#2
updateDataFeedsValuesPartial
#3
updateDataFeedsValuesPartial
#4
updateTemporalNumericValuesV1
#6
setData
#7
0x9f2fad…6fa7
#8
0x138606…6701
#5
0x3f5c179b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x04d9a08c…fe81
0xacc0a0…fd62
2 touches
0 conflicts
0x092c3634…6a5c
0xacc0a0…fd62
2 touches
0 conflicts
0x1347c219…2e22
0xacc0a0…fd62
2 touches
0 conflicts
0x1632adac…6043
0xacc0a0…fd62
2 touches
0 conflicts
0x5250d39b…c3fb
0xacc0a0…fd62
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
0x0000000000…00003d
Audit this contract →
← previous block
·
next block →
recent activity