pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#82,752,664
← previous block
next block →
recent activity
Analyzing
Block #82,752,664
11 transactions · 9 stateful · 2026-06-21 14:04:35 UTC
Parallelism
64
/100
Blocked
33
%
Avg conflicts / tx
0.55
Longest chain
4
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#82,752,664
· 11 txs across 4 waves · depth 4
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
#0
syscallReward
#1
0xab083028
#2
updateDataFeedsValuesPartial
#3
updateDataFeedsValuesPartial
#4
createAccount
· blocks 3
#8
execFwdPositionOps
#9
setData
#10
0xc7e3ec2c
#5
createAccount
· blocks 2
#6
createAccount
· blocks 1
#7
createAccount
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
6
w2
7
w3
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdd4e4728…ec4a
0x000000…012a
8 touches
6 conflicts
0x00000000…00cc
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…00d7
0x34b655…2a6f
8 touches
6 conflicts
0x01d65db5…c625
0x000000…012a
2 touches
0 conflicts
0x3e2da114…bf2f
0x000000…012a
2 touches
0 conflicts
0x9aee4005…12b7
0x000000…012a
2 touches
0 conflicts
0xd9f50d4f…90cc
0x000000…012a
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
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:
AUSD (AUSD)
6 conflicts on slot
0xdd4e4728cf…4aec4a
Audit this contract →
← previous block
·
next block →
recent activity