pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#82,715,406
← previous block
next block →
recent activity
Analyzing
Block #82,715,406
10 transactions · 9 stateful · 2026-06-21 09:55:50 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,715,406
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
withdraw
#2
0xab083028
#3
0x6ad2e98b
#4
0x5a5d9a99
· blocks 1
#6
updateDataFeedsValuesPartial
#7
executeBatch
#8
setData
#9
0x6a37b59e
#5
0x5a5d9a99
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa6464996…3af9
0x34b655…2a6f
4 touches
1 conflict
0x7ba3d4ba…d55a
0xc8689a…ee79
4 touches
1 conflict
0x0efc210e…70ab
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0xfb3a17d6…0b21
0x103222…7496
2 touches
0 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
2 touches
0 conflicts
0x7bdc653c…8eae
0x57ea24…2cec
2 touches
0 conflicts
0xc7cf5a91…60fd
0x57ea24…2cec
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
0xa6464996a2…6f3af9
Audit this contract →
← previous block
·
next block →
recent activity