pev
.
One block, wave by wave
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#80,401,233
← previous block
next block →
recent activity
Analyzing
Block #80,401,233
10 transactions · 8 stateful · 2026-06-10 16:43:33 UTC
Parallelism
80
/100
Blocked
25
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#80,401,233
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execute
#2
execute
#3
0xab083028
· blocks 2
#5
0x39435dac
#7
0x3f5c179b
#8
updateDataFeedsValuesPartial
#9
setData
#4
0xab083028
#6
0x0c7abd22
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x342fbbca…d443
0x40c49f…2af0
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x472bf3c3…467f
0x40c49f…2af0
3 touches
1 conflict
0x3f1434d4…1ce1
0x11ed3b…2c96
2 touches
0 conflicts
0x830d7f41…1934
0x11ed3b…2c96
2 touches
0 conflicts
0x01e7b865…6e6d
0x188d58…ea8e
2 touches
0 conflicts
0x01e7b865…6e6f
0x188d58…ea8e
2 touches
0 conflicts
0x00000000…0000
0x2d59fc…cd50
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:
0x40c49f17…d22af0
1 conflict on slot
0x342fbbca09…fcd443
Audit this contract →
← previous block
·
next block →
recent activity