pev
.
One block, wave by wave
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#80,319,181
← previous block
next block →
recent activity
Analyzing
Block #80,319,181
13 transactions · 8 stateful · 2026-06-10 07:36:46 UTC
Parallelism
77
/100
Blocked
25
%
Avg conflicts / tx
0.23
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#80,319,181
· 13 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0xed82b078
· blocks 2
#3
updateDataFeedsValuesPartial
#4
updateDataFeedsValuesPartial
#5
updateDataFeedsValuesPartial
#7
setData
#8
forward
#9
0x6df9e92b
#10
0xcdbccf…3453
#11
0xf86f9d…37bf
#12
0xc7e3ec2c
#2
0xed82b078
· blocks 1
#6
0xa09e9040
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
6
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…0000
0x019883…2a9a
2 touches
0 conflicts
0x00000000…0002
0x019883…2a9a
2 touches
0 conflicts
0x00000000…0003
0x019883…2a9a
2 touches
0 conflicts
0x0fc5ad2c…736e
0x065c9d…c394
2 touches
0 conflicts
0x222c917d…eb41
0x065c9d…c394
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:
Kuru Exchange: Market-MON/USDC
3 conflicts on slot
0x0000000000…00003d
Audit this contract →
← previous block
·
next block →
recent activity