pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#80,328,533
← previous block
next block →
recent activity
Analyzing
Block #80,328,533
11 transactions · 10 stateful · 2026-06-10 08:39:05 UTC
Parallelism
73
/100
Blocked
20
%
Avg conflicts / tx
0.27
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#80,328,533
· 11 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0xab083028
#2
updateDataFeedsValuesPartial
#3
updateDataFeedsValuesPartial
#4
0x98717539
#5
0x3f5c179b
#6
execute
· blocks 2
#9
0x23afbff3
#10
setData
#7
execute
· blocks 1
#8
execute
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
7
w1
8
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0001
0x24b18e…3301
6 touches
3 conflicts
0x771a3650…01cd
0x3bd359…433a
6 touches
3 conflicts
0x00000000…0000
0x24b18e…3301
6 touches
3 conflicts
0x797464db…e15a
0x788571…8888
6 touches
3 conflicts
0xa743c8dd…ebf2
0x788571…8888
6 touches
3 conflicts
0x01a89030…f786
0x98dc6e…8633
2 touches
0 conflicts
0x0fc41e7b…6831
0x98dc6e…8633
2 touches
0 conflicts
0x5b571ba0…f13a
0x98dc6e…8633
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
3 conflicts on slot
0x0000000000…000001
Audit this contract →
← previous block
·
next block →
recent activity