pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#84,077,703
← previous block
next block →
recent activity
Analyzing
Block #84,077,703
12 transactions · 10 stateful · 2026-06-27 17:31:41 UTC
Parallelism
83
/100
Blocked
10
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#84,077,703
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
0x6ad2e98b
#3
updateDataFeedsValuesPartial
#4
updatePrices
#5
redeemDelegations
#6
forward
#7
0xed82b078
#8
0xed82b078
· blocks 1
#10
0x6a400975
#11
setData
#9
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
8
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3de5fb8b…400a
0xa6afd3…d132
4 touches
1 conflict
0xb3572c95…9c4a
0x2a68ba…90c5
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x4bebdceb…7016
0x065c9d…c394
2 touches
0 conflicts
0xa2b4b35a…9090
0x065c9d…c394
2 touches
0 conflicts
0xc612440e…d44a
0x065c9d…c394
2 touches
0 conflicts
0xea1e8cc3…4db3
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-WETH/USDC
1 conflict on slot
0x3de5fb8b37…25400a
Audit this contract →
← previous block
·
next block →
recent activity