pev
.
One block, wave by wave
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#80,218,841
← previous block
next block →
recent activity
Analyzing
Block #80,218,841
7 transactions · 7 stateful · 2026-06-09 20:27:44 UTC
Parallelism
71
/100
Blocked
14
%
Avg conflicts / tx
0.14
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#80,218,841
· 7 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
0x98717539
· blocks 1
#4
updateDataFeedsValuesPartial
#5
0x6a2877b8
#6
setData
#3
0x98717539
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x90f07a4f…d932
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x11162862…9219
0x34b655…2a6f
2 touches
0 conflicts
0x32bab2a7…9eea
0x34b655…2a6f
2 touches
0 conflicts
0x4139c1b0…7457
0x34b655…2a6f
2 touches
0 conflicts
0x681e29c2…aea4
0x34b655…2a6f
2 touches
0 conflicts
0x6b8cf59b…3192
0x34b655…2a6f
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:
Perpl
1 conflict on slot
0x90f07a4ff9…b3d932
Audit this contract →
← previous block
·
next block →
recent activity