pev
.
One block, wave by wave
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#82,274,199
← previous block
next block →
recent activity
Analyzing
Block #82,274,199
10 transactions · 9 stateful · 2026-06-19 08:48:35 UTC
Parallelism
80
/100
Blocked
11
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#82,274,199
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
· blocks 1
#2
updateDataFeedsValuesPartial
#3
updatePrices
#4
handleOps
#6
0x23afbff3
#7
0x6a3502db
#8
setData
#9
0x39435dac
#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
0xa56a84d2…0dcd
0x000000…a032
2 touches
0 conflicts
0x1b7e14ea…4984
0x065c9d…c394
2 touches
0 conflicts
0x4535cc1a…dfb7
0x065c9d…c394
2 touches
0 conflicts
0x7d8bc9f8…1d4a
0x065c9d…c394
2 touches
0 conflicts
0x557cd4fa…228c
0x2a68ba…90c5
2 touches
0 conflicts
0xd8dd03ce…dc8d
0x2a68ba…90c5
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