pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#76,481,217
← previous block
next block →
recent activity
Analyzing
Block #76,481,217
13 transactions · 8 stateful · 2026-05-23 12:54:52 UTC
Parallelism
85
/100
Blocked
25
%
Avg conflicts / tx
0.15
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#76,481,217
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
· blocks 2
#4
0xe3a3c9cc
#5
updateDataFeedsValuesPartial
#6
updateTemporalNumericValuesV1
#7
createModule
#8
execFwdPositionOps
#9
execFwdPositionOps
#10
setData
#11
exactInputSingle
#12
execOrders
#2
0x0c7abd22
#3
0x719d975a
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7c403af1…31b1
0x3bd359…433a
4 touches
1 conflict
0x18aed20c…48f3
0x000000…012a
4 touches
1 conflict
0x00000000…0000
0xd5b70d…615b
4 touches
1 conflict
0x00000000…0003
0xd5b70d…615b
4 touches
1 conflict
0x00000000…0004
0xd5b70d…615b
4 touches
1 conflict
0x41b1ace5…9a19
0xd32edf…ff58
3 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0013
0x1b6862…e19c
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:
Wrapped MON (WMON)
1 conflict on slot
0x7c403af1e6…1d31b1
Audit this contract →
← previous block
·
next block →
recent activity