pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#80,276,062
← previous block
next block →
recent activity
Analyzing
Block #80,276,062
12 transactions · 10 stateful · 2026-06-10 02:49:16 UTC
Parallelism
75
/100
Blocked
20
%
Avg conflicts / tx
0.25
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#80,276,062
· 12 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#2
approve
· blocks 1
#5
updateDataFeedsValuesPartial
#6
0x98717539
#7
0x0f6795d9
#8
0x0f6795d9
#9
0x6a28d124
#10
0x33ced2…e5ac
#11
setData
#3
deposit
· blocks 1
#4
0xa09e9040
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w0
3
w1
4
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x487d2922…28b6
0x754704…b603
2 touches
1 conflict
0x3f9db95d…a401
0x065c9d…c394
2 touches
0 conflicts
0x4539043a…8df4
0x065c9d…c394
2 touches
0 conflicts
0xc4134f54…e726
0x065c9d…c394
2 touches
0 conflicts
0xe4f25505…b175
0x065c9d…c394
2 touches
0 conflicts
0x00000000…0012
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0013
0x1b6862…e19c
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
1 conflict on slot
0x0000000000…00003d
Audit this contract →
← previous block
·
next block →
recent activity