pev
.
One block, wave by wave
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#82,271,801
← previous block
next block →
recent activity
Analyzing
Block #82,271,801
10 transactions · 9 stateful · 2026-06-19 08:32:40 UTC
Parallelism
80
/100
Blocked
22
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#82,271,801
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
updatePrices
· blocks 1
#4
updatePrices
#5
0xa09e9040
· blocks 1
#7
0x57368ddf
#8
0x6a34ff20
#9
setData
#3
updatePrices
#6
0x23afbff3
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xaa7ee7…f0e4
4 touches
1 conflict
0xf8d169d2…81fb
0x065c9d…c394
4 touches
1 conflict
0xd8dd03ce…dc8d
0x2a68ba…90c5
4 touches
1 conflict
0x57966662…fc57
0x065c9d…c394
2 touches
0 conflicts
0x8309e8ca…5583
0x065c9d…c394
2 touches
0 conflicts
0x01a89030…f786
0x368ee5…7ca4
2 touches
0 conflicts
0x5b571ba0…f13a
0x368ee5…7ca4
2 touches
0 conflicts
0x68faa0b9…14af
0x368ee5…7ca4
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:
0xaa7ee7ce…aff0e4
1 conflict on slot
0x0000000000…000002
Audit this contract →
← previous block
·
next block →
recent activity