pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#75,678,228
← previous block
next block →
recent activity
Analyzing
Block #75,678,228
11 transactions · 10 stateful · 2026-05-19 19:46:16 UTC
Parallelism
82
/100
Blocked
10
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#75,678,228
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x6a0cbe80
#2
removeLiquidity
· blocks 1
#3
0xab083028
#4
0x98717539
#5
updateDataFeedsValuesPartial
#6
0x0c7abd22
#7
cancel
#8
setData
#9
0x39435dac
#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
0x81ce69cb…0e84
0x5afd3e…7620
4 touches
1 conflict
0x923a238b…3c74
0x5afd3e…7620
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x10abefc9…c9bc
0x1d1325…2305
2 touches
0 conflicts
0x10d80fee…dbda
0x1d1325…2305
2 touches
0 conflicts
0x8cf3d245…1d0d
0x1d1325…2305
2 touches
0 conflicts
0xad3ef711…4f2b
0x1d1325…2305
2 touches
0 conflicts
0xdb067026…9eb8
0x1d1325…2305
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
0x81ce69cbd2…430e84
Audit this contract →
← previous block
·
next block →
recent activity