pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#75,468,464
← previous block
next block →
recent activity
Analyzing
Block #75,468,464
11 transactions · 7 stateful · 2026-05-18 20:18:10 UTC
Parallelism
82
/100
Blocked
14
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#75,468,464
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
removeLiquidity
· blocks 1
#3
0x98717539
#4
updateDataFeedsValuesPartial
#5
withdraw
#6
0xa391f92f
#7
commit
#8
setData
#9
0x1489d9…dce3
#10
0x5d2fd812
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x64046a71…92ad
0x5afd3e…7620
4 touches
1 conflict
0x3dc874a4…3ea0
0x5afd3e…7620
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…0012
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0013
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0015
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0018
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0028
0x1b6862…e19c
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
0x64046a71f4…7d92ad
Audit this contract →
← previous block
·
next block →
recent activity