pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#75,989,423
← previous block
next block →
recent activity
Analyzing
Block #75,989,423
15 transactions · 11 stateful · 2026-05-21 06:19:28 UTC
Parallelism
93
/100
Blocked
0
%
Avg conflicts / tx
0
Longest chain
1
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#75,989,423
· 15 txs across 1 wave · depth 1
parallel ↔ serial
wave
w0
#0
syscallReward
#1
0xab083028
#2
execPerpOps
#3
execPerpOps
#4
0xbfd493…8d3c
#5
0x0c7abd22
#6
redeemDelegations
#7
execFwdPositionOps
#8
execFwdPositionOps
#9
updateDataFeedsValuesPartial
#10
setData
#11
execOrders
#12
execOrders
#13
execOrders
#14
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
● no conflicts
every tx in this block runs in parallel
Hot storage slots
Contention
0x09000000…0001
0x000000…1000
2 touches
0 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x4e5bd6a5…2084
0x065c9d…c394
2 touches
0 conflicts
0x6d4f82e3…b42c
0x065c9d…c394
2 touches
0 conflicts
0x7e788582…08db
0x065c9d…c394
2 touches
0 conflicts
0x9b392bc0…df97
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.
← previous block
·
next block →
recent activity