pev
.
One block, wave by wave
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#82,658,020
← previous block
next block →
recent activity
Analyzing
Block #82,658,020
11 transactions · 7 stateful · 2026-06-21 03:32:19 UTC
Parallelism
82
/100
Blocked
29
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#82,658,020
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
removeLiquidity
#2
0x1094dc9f
· blocks 1
#4
0x5a5d9a99
· blocks 1
#5
updateDataFeedsValuesPartial
#6
updateDataFeedsValuesPartial
#7
updateDataFeedsValuesPartial
#9
0x0f6795d9
#10
setData
#3
0xab083028
#8
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
4
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe6805ef8…e22e
0x34b655…2a6f
4 touches
1 conflict
0x2bf5914f…c75d
0x34b655…2a6f
4 touches
1 conflict
0x81a3d790…ed87
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0x8a751d7a…247c
0xa6afd3…d132
4 touches
1 conflict
0x00000000…0001
0x354d92…66fb
2 touches
0 conflicts
0x09000000…0001
0x000000…1000
2 touches
0 conflicts
0x38b5b2ce…c5bb
0x354d92…66fb
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:
Perpl
1 conflict on slot
0xe6805ef89e…4fe22e
Audit this contract →
← previous block
·
next block →
recent activity