pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#80,315,273
← previous block
next block →
recent activity
Analyzing
Block #80,315,273
8 transactions · 6 stateful · 2026-06-10 07:10:44 UTC
Parallelism
75
/100
Blocked
17
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#80,315,273
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
addSellOrder
· blocks 1
#2
updateDataFeedsValuesPartial
#4
setData
#5
0xf0e540…e425
#6
0x71a250…bc58
#7
0xc7e3ec2c
#3
addBuyOrder
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x92339d95…0800
0x0000a8…8888
2 touches
0 conflicts
0x8e3cecd8…18d4
0x065c9d…c394
2 touches
0 conflicts
0xe9b128cc…1e95
0x065c9d…c394
2 touches
0 conflicts
0xf5e44f64…6516
0x065c9d…c394
2 touches
0 conflicts
0xfc66c14a…98d6
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
1 conflict on slot
0x0000000000…00003d
Audit this contract →
← previous block
·
next block →
recent activity