pev
.
One block, wave by wave
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#82,552,992
← previous block
next block →
recent activity
Analyzing
Block #82,552,992
12 transactions · 8 stateful · 2026-06-20 15:48:24 UTC
Parallelism
83
/100
Blocked
13
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#82,552,992
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
0x40e79b1b
· blocks 1
#4
0x0f6795d9
#5
0x0f6795d9
#6
0x0f6795d9
#7
updateDataFeedsValuesPartial
#8
updateDataFeedsValuesPartial
#9
execute
#10
0x6a36b6c0
#11
setData
#3
0x40e79b1b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x557cd4fa…228c
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x831baebe…eb9d
0x065c9d…c394
3 touches
1 conflict
0xf28a2bdf…9743
0x065c9d…c394
3 touches
1 conflict
0x01e7b865…6e6d
0x188d58…ea8e
2 touches
0 conflicts
0x01e7b865…6e6e
0x188d58…ea8e
2 touches
0 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
2 touches
0 conflicts
0x09106a95…1467
0x33176b…e078
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: MarginAccount
1 conflict on slot
0x557cd4fad5…e4228c
Audit this contract →
← previous block
·
next block →
recent activity