pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#84,331,788
← previous block
next block →
recent activity
Analyzing
Block #84,331,788
11 transactions · 8 stateful · 2026-06-28 21:44:14 UTC
Parallelism
82
/100
Blocked
13
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#84,331,788
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
removeLiquidityNATIVE
· blocks 1
#3
0xab083028
#4
0x98717539
#5
updateDataFeedsValuesPartial
#6
updateDataFeedsValuesPartial
#7
0x62be7533
#8
setData
#9
execOrders
#10
0x50a0b275
#2
removeLiquidity
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x06ba83ca…9a08
0x5afd3e…7620
4 touches
1 conflict
0x5d82c9b5…004c
0x3bd359…433a
4 touches
1 conflict
0x450cb620…65b1
0x5afd3e…7620
4 touches
1 conflict
0x00000000…0004
0x5afd3e…7620
4 touches
1 conflict
0x75194ada…a1c5
0x34b655…2a6f
2 touches
0 conflicts
0x404314de…df1a
0x3bd359…433a
2 touches
0 conflicts
0x27ad8df9…5d18
0x5afd3e…7620
2 touches
0 conflicts
0xf0b36a1c…dd4d
0x5afd3e…7620
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
0x06ba83ca23…4b9a08
Audit this contract →
← previous block
·
next block →
recent activity