pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#75,470,850
← previous block
next block →
recent activity
Analyzing
Block #75,470,850
14 transactions · 10 stateful · 2026-05-18 20:34:03 UTC
Parallelism
86
/100
Blocked
10
%
Avg conflicts / tx
0.07
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#75,470,850
· 14 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x42dd8743
#2
removeLiquidity
· blocks 1
#3
0x5bf9264c
#4
updateDataFeedsValuesPartial
#5
0x0c7abd22
#6
0x5339c59f
#7
0xed82b078
#8
transfer
#9
0xe9316489
#10
0xd86335…2368
#11
0x656a0b…bdfe
#12
setData
#13
0x5d2fd812
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
13
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa6ae4819…b723
0x5afd3e…7620
4 touches
1 conflict
0x0729acf6…c72d
0x5afd3e…7620
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…0003
0x0594c7…a3be
2 touches
0 conflicts
0x00000000…0004
0x0594c7…a3be
2 touches
0 conflicts
0x00000000…0005
0x0594c7…a3be
2 touches
0 conflicts
0x1fdfa53b…abfb
0x0594c7…a3be
2 touches
0 conflicts
0xd5f56205…6498
0x0594c7…a3be
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
0xa6ae4819cd…6cb723
Audit this contract →
← previous block
·
next block →
recent activity