pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#75,302,834
← previous block
next block →
recent activity
Analyzing
Block #75,302,834
14 transactions · 11 stateful · 2026-05-18 01:51:04 UTC
Parallelism
79
/100
Blocked
18
%
Avg conflicts / tx
0.14
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#75,302,834
· 14 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0xa96df62f
#2
execute
#3
addLiquidity
· blocks 1
#4
updateDataFeedsValuesPartial
#5
0x000000b2
#6
0x0c7abd22
#8
0x6a0a7100
#9
setData
#11
0x39435dac
#12
jMMeC
#13
execute
#7
0x62be7533
· blocks 1
#10
bridge
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
7
w1
10
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0004
0x5afd3e…7620
4 touches
1 conflict
0x4039b31f…0f4a
0x754704…b603
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x4df5df22…187e
0x188d58…ea8e
2 touches
0 conflicts
0x4df5df22…187f
0x188d58…ea8e
2 touches
0 conflicts
0xe75ce681…ba5f
0x188d58…ea8e
2 touches
0 conflicts
0xe75ce681…ba60
0x188d58…ea8e
2 touches
0 conflicts
0xe75ce681…ba62
0x188d58…ea8e
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:
Liquidity Book Token (LBT)
1 conflict on slot
0x0000000000…000004
Audit this contract →
← previous block
·
next block →
recent activity