pev
.
One block, wave by wave
→
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#80,058,180
← previous block
next block →
recent activity
Analyzing
Block #80,058,180
11 transactions · 10 stateful · 2026-06-09 02:37:06 UTC
Parallelism
82
/100
Blocked
10
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#80,058,180
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
updateDataFeedsValuesPartial
#3
0x77813803
· blocks 1
#5
0x98717539
#6
poke
#7
0x3f5c179b
#8
executeBatch
#9
0x0c7abd22
#10
setData
#4
0x1a945f9c
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd8eb2d31…2ac0
0xea1b8e…c5ec
4 touches
1 conflict
0xeef70cb9…5de7
0xea1b8e…c5ec
4 touches
1 conflict
0x455b104f…3960
0xea1b8e…c5ec
4 touches
1 conflict
0xbc33a929…8b24
0xea1b8e…c5ec
4 touches
1 conflict
0x71729695…12ca
0x1efe02…37d6
2 touches
0 conflicts
0xb38fc90d…c9e4
0x1efe02…37d6
2 touches
0 conflicts
0xb516caea…5cbd
0x1efe02…37d6
2 touches
0 conflicts
0x0fc41e7b…6831
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:
LeverUp: LeverUp
1 conflict on slot
0xd8eb2d31c2…a32ac0
Audit this contract →
← previous block
·
next block →
recent activity