pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#80,328,489
← previous block
next block →
recent activity
Analyzing
Block #80,328,489
11 transactions · 11 stateful · 2026-06-10 08:38:48 UTC
Parallelism
82
/100
Blocked
9
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#80,328,489
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execute
#2
0xab083028
#3
0x5bf9264c
#4
0x0c7abd22
#5
execute
· blocks 1
#7
forward
#8
updateDataFeedsValuesPartial
#9
claimRakeback
#10
setData
#6
execute
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0000
0x24b18e…3301
4 touches
1 conflict
0x00000000…0001
0x24b18e…3301
4 touches
1 conflict
0x797464db…e15a
0x788571…8888
4 touches
1 conflict
0xa743c8dd…ebf2
0x788571…8888
4 touches
1 conflict
0x771a3650…01cd
0x3bd359…433a
4 touches
1 conflict
0xc0b80d49…be68
0x065c9d…c394
2 touches
0 conflicts
0xf3e56233…2744
0x065c9d…c394
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:
0x24b18eb6…733301
1 conflict on slot
0x0000000000…000000
Audit this contract →
← previous block
·
next block →
recent activity