pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#80,270,260
← previous block
next block →
recent activity
Analyzing
Block #80,270,260
9 transactions · 7 stateful · 2026-06-10 02:10:37 UTC
Parallelism
78
/100
Blocked
29
%
Avg conflicts / tx
0.22
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#80,270,260
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
· blocks 1
#2
updateDataFeedsValuesPartial
#3
updateDataFeedsValuesPartial
#4
0x6a28c814
· blocks 1
#5
0x3f5c179b
#7
setData
#6
0x3f5c179b
#8
0x6a28c815
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
4
w0
6
w1
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x179fe783…6945
0xa6afd3…d132
4 touches
1 conflict
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
2 touches
0 conflicts
0x1ea0a6bc…6a74
0x2a68ba…90c5
2 touches
0 conflicts
0x8876d94c…8435
0x2a68ba…90c5
2 touches
0 conflicts
0x00000000…0004
0x546d22…8146
2 touches
0 conflicts
0x40970e69…da50
0x69df8a…6292
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
0x179fe7837f…326945
Audit this contract →
← previous block
·
next block →
recent activity