pev
.
One block, wave by wave
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#75,014,382
← previous block
next block →
recent activity
Analyzing
Block #75,014,382
7 transactions · 6 stateful · 2026-05-16 17:44:43 UTC
Parallelism
71
/100
Blocked
17
%
Avg conflicts / tx
0.14
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#75,014,382
· 7 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x98717539
#2
swapExactETHForTokensSupportingFeeOnTransferTokens
· blocks 1
#4
updateDataFeedsValuesPartial
#5
updateDataFeedsValuesPartial
#6
setData
#3
swapExactETHForTokensSupportingFeeOnTransferTokens
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb34209a2…164d
0x402807…5159
4 touches
1 conflict
0x00000000…0008
0x509771…3c7b
4 touches
1 conflict
0x21c137b8…3a77
0x3bd359…433a
4 touches
1 conflict
0x4d394876…c488
0x402807…5159
4 touches
1 conflict
0x2484cc15…5afc
0x34b655…2a6f
2 touches
0 conflicts
0x7cb2f3fa…4836
0x34b655…2a6f
2 touches
0 conflicts
0x00000000…0009
0x509771…3c7b
2 touches
0 conflicts
0x00000000…000a
0x509771…3c7b
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
0xb34209a263…ad164d
Audit this contract →
← previous block
·
next block →
recent activity