pev
.
One block, wave by wave
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#80,693,830
← previous block
next block →
recent activity
Analyzing
Block #80,693,830
10 transactions · 9 stateful · 2026-06-12 01:15:01 UTC
Parallelism
80
/100
Blocked
11
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#80,693,830
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
removeLiquidityNATIVE
#2
0x98717539
· blocks 1
#4
0x98717539
#5
updateDataFeedsValuesPartial
#6
0x3f5c179b
#7
setData
#8
0x39435dac
#9
0xc7e3ec2c
#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
0x21fae19a…0b14
0x34b655…2a6f
2 touches
0 conflicts
0x2484cc15…5afc
0x34b655…2a6f
2 touches
0 conflicts
0x5d82c9b5…004c
0x3bd359…433a
2 touches
0 conflicts
0x00000000…0004
0x5afd3e…7620
2 touches
0 conflicts
0x3fa79f0e…92a4
0x5afd3e…7620
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