pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#75,016,346
← previous block
next block →
recent activity
Analyzing
Block #75,016,346
8 transactions · 7 stateful · 2026-05-16 17:57:56 UTC
Parallelism
75
/100
Blocked
14
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#75,016,346
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x6a08b09c
#2
updatePosition
#3
swapExactETHForTokensSupportingFeeOnTransferTokens
· blocks 1
#5
updateDataFeedsValuesPartial
#6
setData
#7
execOrders
#4
swapExactETHForTokensSupportingFeeOnTransferTokens
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4d394876…c488
0x402807…5159
4 touches
1 conflict
0xb34209a2…164d
0x402807…5159
4 touches
1 conflict
0x00000000…0008
0x509771…3c7b
4 touches
1 conflict
0x21c137b8…3a77
0x3bd359…433a
4 touches
1 conflict
0xd1a0adf6…6e55
0x54cd53…9e7d
2 touches
0 conflicts
0x04ef71e4…cb43
0x6657d1…8ccc
2 touches
0 conflicts
0x0ff53b18…56b9
0x6657d1…8ccc
2 touches
0 conflicts
0x1074892b…40f0
0x6657d1…8ccc
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:
OCTOMON (OCTOMON)
1 conflict on slot
0x4d3948760c…2ac488
Audit this contract →
← previous block
·
next block →
recent activity