pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#75,015,749
← previous block
next block →
recent activity
Analyzing
Block #75,015,749
8 transactions · 6 stateful · 2026-05-16 17:53:56 UTC
Parallelism
75
/100
Blocked
17
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#75,015,749
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x1a945f9c
#2
0x98717539
#3
0x98717539
#4
updateDataFeedsValuesPartial
#5
swapExactETHForTokensSupportingFeeOnTransferTokens
· blocks 1
#7
setData
#6
swapExactETHForTokensSupportingFeeOnTransferTokens
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
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
0x3dbd9177…e936
0xea1b8e…c5ec
2 touches
0 conflicts
0x455b104f…3960
0xea1b8e…c5ec
2 touches
0 conflicts
0xa8abcc19…3d83
0xea1b8e…c5ec
2 touches
0 conflicts
0xaa2f6971…c549
0xea1b8e…c5ec
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