pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#82,513,106
← previous block
next block →
recent activity
Analyzing
Block #82,513,106
9 transactions · 8 stateful · 2026-06-20 11:22:34 UTC
Parallelism
78
/100
Blocked
13
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#82,513,106
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#2
updateDataFeedsValuesPartial
#3
updateDataFeedsValuesPartial
#4
0x5a5d9a99
#6
setData
#7
updatePriceFeedsIfNecessary
#8
0xc7e3ec2c
#5
0x40e79b1b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
5
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
0x4df9258c…6c65
0x065c9d…c394
2 touches
0 conflicts
0xba4f1005…3cd6
0x065c9d…c394
2 touches
0 conflicts
0xc5414c3e…94d2
0x065c9d…c394
2 touches
0 conflicts
0xe542ecb9…0eff
0x065c9d…c394
2 touches
0 conflicts
0x00000000…0012
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