pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#77,784,787
← previous block
next block →
recent activity
Analyzing
Block #77,784,787
11 transactions · 10 stateful · 2026-05-29 13:41:13 UTC
Parallelism
82
/100
Blocked
10
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#77,784,787
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x39ecce49
· blocks 1
#3
0xab083028
#4
updateDataFeedsValuesPartial
#5
updateDataFeedsValuesPartial
#6
redeemDelegations
#7
0x3f5c179b
#8
execFwdPositionOps
#9
execFwdPositionOps
#10
setData
#2
0x39ecce49
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0000
0x139aab…382b
4 touches
1 conflict
0x00000000…0001
0x139aab…382b
4 touches
1 conflict
0x3c251e5a…0218
0x6a13bf…7777
4 touches
1 conflict
0x877b0dd6…84c6
0x3bd359…433a
4 touches
1 conflict
0x00000000…0003
0x139aab…382b
4 touches
1 conflict
0x259ee49c…49df
0x69df8a…6292
2 touches
0 conflicts
0x4e804b48…ef71
0x69df8a…6292
2 touches
0 conflicts
0xcfe06a18…b5b5
0x69df8a…6292
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:
Capricorn: WMON/SHARKIE Pool (1%)
1 conflict on slot
0x0000000000…000000
Audit this contract →
← previous block
·
next block →
recent activity