pev
.
One block, wave by wave
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#80,982,039
← previous block
next block →
recent activity
Analyzing
Block #80,982,039
14 transactions · 8 stateful · 2026-06-13 09:16:36 UTC
Parallelism
86
/100
Blocked
13
%
Avg conflicts / tx
0.07
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#80,982,039
· 14 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
____MEV_X____Ga543
· blocks 1
#2
0x719d975a
#3
0x0f052239
#4
0x05ee6a22
#6
0xed82b078
#7
updateDataFeedsValuesPartial
#8
updateDataFeedsValuesPartial
#9
0x62be7533
#10
forward
#11
forward
#12
0x6a2d206c
#13
setData
#5
0x13572d0b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x490911cc…5fea
0x0c65a0…0852
4 touches
1 conflict
0x5860c4f3…0c39
0x3bd359…433a
4 touches
1 conflict
0x00000000…0000
0xbab229…9388
4 touches
1 conflict
0x00000000…0001
0xbab229…9388
4 touches
1 conflict
0x00000000…0003
0xbab229…9388
4 touches
1 conflict
0x373f94db…c177
0x3bd359…433a
2 touches
0 conflicts
0x391d170b…bd0f
0x3bd359…433a
2 touches
0 conflicts
0x3de215fe…c018
0x3bd359…433a
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:
0x0c65a0bc…0e0852
1 conflict on slot
0x490911ccd2…a15fea
Audit this contract →
← previous block
·
next block →
recent activity