pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#84,063,820
← previous block
next block →
recent activity
Analyzing
Block #84,063,820
9 transactions · 7 stateful · 2026-06-27 15:59:18 UTC
Parallelism
78
/100
Blocked
14
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#84,063,820
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
rebalance
#2
updateDataFeedsValuesPartial
#3
updatePriceFeedsIfNecessary
#4
0xed82b078
· blocks 1
#5
0xed82b078
#7
0x6a3ff3ce
#8
setData
#6
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xff96dc9b…93d7
0x065c9d…c394
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00f7e3b7…e018
0x188d58…ea8e
2 touches
0 conflicts
0x13fcf720…63a3
0x188d58…ea8e
2 touches
0 conflicts
0x198ca230…16df
0x188d58…ea8e
2 touches
0 conflicts
0x19fd1250…1b79
0x188d58…ea8e
2 touches
0 conflicts
0x1af18a2d…e5bd
0x188d58…ea8e
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
0xff96dc9b2f…5a93d7
Audit this contract →
← previous block
·
next block →
recent activity