pev
.
One block, wave by wave
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#82,253,944
← previous block
next block →
recent activity
Analyzing
Block #82,253,944
10 transactions · 9 stateful · 2026-06-19 06:33:25 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,253,944
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
· blocks 1
#2
updateDataFeedsValuesPartial
#3
updateDataFeedsValuesPartial
#5
buy
#6
0x6a34e32d
#7
setData
#8
redeemDelegations
#9
0x39435dac
#4
0x3f5c179b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0fde64da…aa3e
0x2a68ba…90c5
4 touches
1 conflict
0x99ecae25…abb9
0x851145…3f07
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0x4661ad10…750e
0x851145…3f07
3 touches
1 conflict
0x62811193…1867
0x69df8a…6292
2 touches
0 conflicts
0x62811193…1868
0x69df8a…6292
2 touches
0 conflicts
0x62811193…1869
0x69df8a…6292
2 touches
0 conflicts
0x6cd67eff…f738
0x69df8a…6292
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
0x0fde64da0b…a5aa3e
Audit this contract →
← previous block
·
next block →
recent activity