pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#87,754,144
← previous block
next block →
recent activity
Analyzing
Block #87,754,144
24 transactions · 22 stateful · 2026-07-14 18:31:30 UTC
Parallelism
83
/100
Blocked
36
%
Avg conflicts / tx
0.46
Longest chain
4
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#87,754,144
· 24 txs across 4 waves · depth 4
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
#0
syscallReward
#1
0xab083028
· blocks 2
#2
updatePrices
#3
updatePrices
#4
execOrders
· blocks 2
#5
execPerpOps
#6
execPerpOps
#7
0x5a5d9a99
· blocks 1
#8
0x5a5d9a99
#10
updateDataFeedsValuesPartial
#11
updateDataFeedsValuesPartial
#15
0x3f5c179b
#18
redeemPyToToken
#19
forward
#20
0x6a5680f9
#21
setData
#9
0x98717539
· blocks 1
#12
execFwdPositionOps
· blocks 2
#14
0x3f5c179b
· blocks 1
#22
execOrders
· blocks 1
#13
execFwdPositionOps
· blocks 1
#16
batchUpdate
#23
execOrders
#17
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
4
w0
7
w0
9
w1
12
w1
13
w2
14
w1
16
w2
17
w3
22
w1
23
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfa551be3…a911
0xa6afd3…d132
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4ab
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x1a287886…0266
0xa6afd3…d132
6 touches
3 conflicts
0x3e8b3a49…53ee
0x34b655…2a6f
4 touches
1 conflict
0x64929e6e…cf16
0x34b655…2a6f
4 touches
1 conflict
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:
Kuru Exchange: Market-WETH/USDC
3 conflicts on slot
0xfa551be3e9…caa911
Audit this contract →
← previous block
·
next block →
recent activity