pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#80,103,468
← previous block
next block →
recent activity
Analyzing
Block #80,103,468
6 transactions · 5 stateful · 2026-06-09 07:38:46 UTC
Parallelism
67
/100
Blocked
20
%
Avg conflicts / tx
0.17
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#80,103,468
· 6 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#3
updateDataFeedsValuesPartial
#4
updateDataFeedsValuesPartial
#5
setData
#2
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5540f956…69e8
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x08c8d9b3…e032
0x065c9d…c394
2 touches
0 conflicts
0x39bc282c…5708
0x065c9d…c394
2 touches
0 conflicts
0x8dd3cce7…2520
0x065c9d…c394
2 touches
0 conflicts
0xa9e137ef…cecf
0x065c9d…c394
2 touches
0 conflicts
0xd89afc07…0aa4
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
0x5540f95607…2d69e8
Audit this contract →
← previous block
·
next block →
recent activity