pev
.
One block, wave by wave
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#75,510,848
← previous block
next block →
recent activity
Analyzing
Block #75,510,848
13 transactions · 9 stateful · 2026-05-19 01:06:56 UTC
Parallelism
85
/100
Blocked
11
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#75,510,848
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xa96df62f
#2
0x1094dc9f
#3
removeLiquidity
· blocks 1
#4
updateDataFeedsValuesPartial
#5
0x0c7abd22
#6
0xed82b078
#7
0x6a0bb828
#8
0x1dd399…ec23
#9
0xdd707d…f4c2
#10
setData
#11
0x39435dac
#12
0x5d2fd812
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
12
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaeb6624d…f1a3
0x5afd3e…7620
4 touches
1 conflict
0x7f87bea7…8f3f
0x5afd3e…7620
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x335a161d…fe7f
0x000000…012a
2 touches
0 conflicts
0x78ae17f2…53be
0x000000…012a
2 touches
0 conflicts
0x00000000…0001
0x010592…1c83
2 touches
0 conflicts
0x00000000…0006
0x010592…1c83
2 touches
0 conflicts
0x27d654d1…b2eb
0x010592…1c83
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
0xaeb6624d4b…76f1a3
Audit this contract →
← previous block
·
next block →
recent activity