pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#75,683,560
← previous block
next block →
recent activity
Analyzing
Block #75,683,560
12 transactions · 9 stateful · 2026-05-19 20:21:40 UTC
Parallelism
83
/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,683,560
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
removeLiquidity
· blocks 1
#2
0x5bf9264c
#3
0x5bf9264c
#4
0x0f6795d9
#5
0x0f6795d9
#6
0x45761772
#7
0xd10227eb
#8
updateDataFeedsValuesPartial
#9
setData
#10
0x62d0f5…853d
#11
0x5d2fd812
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
11
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6091e7f0…d29a
0x5afd3e…7620
4 touches
1 conflict
0x9a8d7b26…91e9
0x5afd3e…7620
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x441ebe8e…c411
0x34b655…2a6f
2 touches
0 conflicts
0x482471ad…122f
0x34b655…2a6f
2 touches
0 conflicts
0x48e4e1cf…f91b
0x34b655…2a6f
2 touches
0 conflicts
0xea02471d…1539
0x34b655…2a6f
2 touches
0 conflicts
0x404314de…df1a
0x3bd359…433a
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
0x6091e7f0ee…b9d29a
Audit this contract →
← previous block
·
next block →
recent activity