pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#82,019,531
← previous block
next block →
recent activity
Analyzing
Block #82,019,531
13 transactions · 8 stateful · 2026-06-18 04:30:14 UTC
Parallelism
92
/100
Blocked
0
%
Avg conflicts / tx
0
Longest chain
1
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#82,019,531
· 13 txs across 1 wave · depth 1
parallel ↔ serial
wave
w0
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
updatePrices
#3
execPerpOps
#4
execPerpOps
#5
0x2993270a
#6
0x39abec6b
#7
0x3f5c179b
#8
0xa0b27d…4ecc
#9
0xac3feb…dd35
#10
0x68c82e…e590
#11
0xe70d90…8697
#12
setData
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
● no conflicts
every tx in this block runs in parallel
Hot storage slots
Contention
0x09000000…0001
0x000000…1000
2 touches
0 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x07d64d54…6bfc
0x2ab50b…5c41
2 touches
0 conflicts
0x080c1dbe…ba16
0x2ab50b…5c41
2 touches
0 conflicts
0x0f723afb…8158
0x2ab50b…5c41
2 touches
0 conflicts
0x24d13a63…cf21
0x2ab50b…5c41
2 touches
0 conflicts
0x28b1af3b…a331
0x2ab50b…5c41
2 touches
0 conflicts
0xc824469a…641c
0x34b655…2a6f
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.
← previous block
·
next block →
recent activity