pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#81,481,622
← previous block
next block →
recent activity
Analyzing
Block #81,481,622
14 transactions · 11 stateful · 2026-06-15 16:44:06 UTC
Parallelism
79
/100
Blocked
18
%
Avg conflicts / tx
0.21
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#81,481,622
· 14 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
execute
#2
0x6a302c4e
#3
0xed82b078
#4
updateDataFeedsValuesPartial
#5
updatePrices
#6
updatePrices
#7
updatePrices
#8
execOrders
· blocks 2
#9
updateDataFeedsValuesPartial
#11
0xaf47a8bb
#12
setData
#10
0x98717539
· blocks 1
#13
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
8
w0
10
w1
13
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa7013be2…c0a8
0x34b655…2a6f
6 touches
3 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0xce827910…ff22
0x065c9d…c394
2 touches
0 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
2 touches
0 conflicts
0x3ce98929…9a9b
0x34b655…2a6f
2 touches
0 conflicts
0x4048db89…30c3
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.
The bottleneck
Throughput-killer:
Perpl
3 conflicts on slot
0xa7013be2a1…9ac0a8
Audit this contract →
← previous block
·
next block →
recent activity