pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#70,982,307
← previous block
next block →
recent activity
Analyzing
Block #70,982,307
12 transactions · 11 stateful · 2026-04-28 01:35:05 UTC
Parallelism
83
/100
Blocked
9
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#70,982,307
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
removeLiquidity
· blocks 1
#2
0x98717539
#3
0x6463ffd1
#4
forward
#5
updateDataFeedsValuesPartial
#6
setData
#7
0x39435dac
#8
0x39435dac
#9
0x39435dac
#10
0x39435dac
#11
0xf2eaccd1
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
0x00000000…0004
0x5afd3e…7620
4 touches
1 conflict
0x4039b31f…0f4a
0x754704…b603
4 touches
1 conflict
0xec423e47…dca3
0x5afd3e…7620
4 touches
1 conflict
0x3e4dfd22…1f91
0x34b655…2a6f
2 touches
0 conflicts
0x414e9446…4b59
0x34b655…2a6f
2 touches
0 conflicts
0x904fc3c0…00ec
0x34b655…2a6f
2 touches
0 conflicts
0xa4561749…e1fa
0x34b655…2a6f
2 touches
0 conflicts
0xb3138aaf…edb3
0x34b655…2a6f
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
0x0000000000…000004
Audit this contract →
← previous block
·
next block →
recent activity