pev
.
One block, wave by wave
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#80,491,518
← previous block
next block →
recent activity
Analyzing
Block #80,491,518
19 transactions · 16 stateful · 2026-06-11 02:45:04 UTC
Parallelism
84
/100
Blocked
19
%
Avg conflicts / tx
0.21
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#80,491,518
· 19 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x0c7abd22
#2
execute
#3
0x5339c59f
· blocks 2
#4
0x5339c59f
· blocks 1
#7
updateDataFeedsValuesPartial
#8
updateDataFeedsValuesPartial
#9
0x3f5c179b
#10
0x0f6795d9
#11
0x0f6795d9
#13
forward
#14
0xe9316489
#15
setData
#16
0x552fd6…8ec8
#17
0x39435dac
#18
0xc7e3ec2c
#5
0xed82b078
· blocks 1
#6
0xed82b078
#12
0x3f5c179b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w0
5
w1
6
w1
12
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa973fa68…f94d
0xa6afd3…d132
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0xb3572c95…9c4a
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…001c
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…002c
0x1b6862…e19c
2 touches
0 conflicts
0xba5743c7…21c3
0x1b6862…e19c
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:
Kuru Exchange: Market-WETH/USDC
3 conflicts on slot
0xa973fa687b…98f94d
Audit this contract →
← previous block
·
next block →
recent activity