pev
.
One block, wave by wave
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#80,931,628
← previous block
next block →
recent activity
Analyzing
Block #80,931,628
9 transactions · 7 stateful · 2026-06-13 03:40:45 UTC
Parallelism
78
/100
Blocked
14
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#80,931,628
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
forward
#2
setData
#3
updateDataFeedsValuesPartial
#4
0x98717539
#5
0x98717539
· blocks 1
#7
0x6a2cd1b5
#8
0xc7e3ec2c
#6
0x98717539
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc38151f2…2bcb
0xc8689a…ee79
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x25d30ad6…a8ec
0x34b655…2a6f
2 touches
0 conflicts
0x61589664…4bd6
0x34b655…2a6f
2 touches
0 conflicts
0x90f07a4f…d932
0x34b655…2a6f
2 touches
0 conflicts
0xb4e0a934…5fc7
0x34b655…2a6f
2 touches
0 conflicts
0xd0ba6b93…bb4d
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: Settlement / Helper
1 conflict on slot
0xc38151f296…e92bcb
Audit this contract →
← previous block
·
next block →
recent activity