pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#80,408,046
← previous block
next block →
recent activity
Analyzing
Block #80,408,046
12 transactions · 9 stateful · 2026-06-10 17:28:54 UTC
Parallelism
75
/100
Blocked
22
%
Avg conflicts / tx
0.17
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#80,408,046
· 12 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0xaf5e395a
· blocks 1
#2
execute302
#4
updateDataFeedsValuesPartial
#5
updateDataFeedsValuesPartial
#6
0x62be7533
#8
forward
#9
0x0f6795d9
#10
0x0f6795d9
#11
setData
#3
0xab083028
· blocks 1
#7
0x0c7abd22
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w1
7
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd16df6cd…5532
0x40c49f…2af0
4 touches
1 conflict
0xf5310ef7…485a
0x40c49f…2af0
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0x00000000…0004
0x0594c7…a3be
2 touches
0 conflicts
0x00000000…0005
0x0594c7…a3be
2 touches
0 conflicts
0x904453c8…4dee
0x0594c7…a3be
2 touches
0 conflicts
0xb7ab1c14…295c
0x0594c7…a3be
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:
0x40c49f17…d22af0
1 conflict on slot
0xd16df6cdbe…065532
Audit this contract →
← previous block
·
next block →
recent activity