pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#82,640,823
← previous block
next block →
recent activity
Analyzing
Block #82,640,823
11 transactions · 10 stateful · 2026-06-21 01:37:01 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
#82,640,823
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
execute
#3
updateDataFeedsValuesPartial
#4
updateDataFeedsValuesPartial
#5
updateDataFeedsValuesPartial
#6
removeLiquidityNATIVE
· blocks 1
#7
0x6a3740b5
#8
setData
#9
0x39435dac
#10
0x5d2fd812
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2d10579…90ef
0x5afd3e…7620
4 touches
1 conflict
0x25da80d1…49ae
0x5afd3e…7620
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x12309510…0ac2
0x000000…012a
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x5cbb39ac…fa8d
0x065c9d…c394
2 touches
0 conflicts
0x5dcd28a7…451d
0x065c9d…c394
2 touches
0 conflicts
0x98e3c27a…7a3a
0x065c9d…c394
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
0xf2d1057905…4590ef
Audit this contract →
← previous block
·
next block →
recent activity